Thanks
Bill. I just read through the ERecover Plan.doc and now understand why I can't
use the recovery as a hot spare. One other question. When I installed Exchange
5.5 on the recovery I was logged on as an administrator, with full rights to the
domain. After the install, I logged on using the service account and
password. Have I inadvertently shot myself in the foot?
Thanks.
List Charter and FAQ at:-----Original Message-----
From: Bill Higgins [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 23, 2001 8:48 AM
To: MS-Exchange Admin Issues
Subject: RE: Mailbox Recovery ServerStandalone Server: not part of a domainMember Server: part of a domainThe reason you have to rebuild it is because you can only restore the DS to the same "named" server. IE: if your Exchange server is "EXCHANGE1", the DS will only restore to a server called "Exchange1"Make sure that your recovery server (and your hot spare if you decided to build one) are at the same Service Pack level, both OS and Exchange SP.Quick and dirty Recovery Server1) lay down OS2) service pack to the appropiate level3) Install Exchange, do not join your org, install using the same org and site name as production, use your production service account/password4) Exchange Service pack5) restore your IS6) run consistency AdjusterHot Spare1) lay down OS2) service pack to appropite level3) wait until you have a catastrophic failure of your exchange server4) Change IP address to your failed exchange server5) rename server to be the same name as your failed exchange server6) install Exchange using the org site as your production, use your production service account/password7) restore IS and DS8) run consistency AdjusterMore details in the whitepapers... be sure to read through them carefully...List Charter and FAQ at:-----Original Message-----
From: Stephen J. Norton [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 23, 2001 05:37
To: MS-Exchange Admin Issues
Subject: RE: Mailbox Recovery ServerThanks Bill. It is 5.5. The stand alone server is part of my domain. I'll read the papers to answer why I need to rebuild to put it into production. The virus scanning is just a chance to work with Antigen, which I have never used.List Charter and FAQ at:-----Original Message-----
From: Bill Higgins [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 23, 2001 8:26 AM
To: MS-Exchange Admin Issues
Subject: RE: Mailbox Recovery ServerYou never mentioned what version of Exchange.For 5.5, start here http://www.microsoft.com/Exchange/techinfo/administration/55/Disaster.asp and http://www.microsoft.com/Exchange/techinfo/administration/55/backuprestore.aspTo answer some of your questions1) Your standalone server will have to be part of your domain2) you do not need connectors3) there shouldn't be any problems, but you do not need any connectors4) you will not be able to use your recovery server as a temporary production server without rebuilding it5) You do not need virus scanning on your recovery server.Read through the whitepapers. There is a big difference between a recovery server and a "hot spare" for production...List Charter and FAQ at:-----Original Message-----
From: Stephen J. Norton [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 23, 2001 04:45
To: MS-Exchange Admin Issues
Subject: Mailbox Recovery ServerList Charter and FAQ at:I'm in the process of building a mailbox recovery server. This machine is a PIII 733 w/ 256 Ram and two ATA 100 IDE drives. First drive is partitioned for the OS and logs, second for the databases. This box is on our network as a stand alone server. It is configured with same service packs as the production box.My current production server runs an Internet Mail Service and Right Fax connector.Am I correct in assuming I do not need to install any connectors on the recovery server in order to restore the database and recover a mailbox to export to a .PST?If I do install the connectors on the recovery server, has anyone had any experience with regards to conflicts in this type of environment with the production server?If I do install the connectors on the recovery server and my production server fails, can I run the recovery server as a temporary production server while the failed server is being repaired? I know the recovery server will be slower due to the IDE drives. I believe I should be able to point everyone's Outlook 2000 to the recovery server and at least have basic, if slow email capabilities.Lastly, I run InnoculatIT on all servers and desktops. I've spoken with Antigen and they have a 30 eval that I can download and install on my recovery server. Any thoughts on that?Thanks in advance for your wisdom and patience.
http://www.sunbelt-software.com/exchange_list_charter.htm
http://www.sunbelt-software.com/exchange_list_charter.htm
http://www.sunbelt-software.com/exchange_list_charter.htm
http://www.sunbelt-software.com/exchange_list_charter.htm
http://www.sunbelt-software.com/exchange_list_charter.htm
