Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php on line 1505 Call Stack: 0.0001 326800 1. {main}() /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:0 0.0003 327652 2. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:25 0.0004 328940 3. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php:20 0.0011 403244 4. vB_Registry->vB_Registry() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php:43 0.0012 403900 5. vB_Input_Cleaner->vB_Input_Cleaner() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php:2337
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /archive/global.php on line 26

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3113

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265
Exchange Server Crashed - Hardware [Archive] - MCSE

PDA

View Full Version : Exchange Server Crashed - Hardware


Gabe Matteson
03-23-04, 12:22 PM
something
Last night out Exchange server (2003) blew up, literally. The only things we
have for a backup is a clean Windows 2003 standard edition ghost image and
the information store and logs (full backup) from the night before. when i
run the disasterrecovery switch is tells me to go to the control panel i
assume to reinstall it? the long and short is, how will installing exchange
on the server (exactly the same) affect the configuration stored in active
directory?
-gm

Gabe Matteson
03-23-04, 01:30 PM
something
Resovled -

"Gabe Matteson" <gmatteson@nospam.cox.net> wrote in message
news:eEmQ6UPEEHA.3568@tk2msftngp13.phx.gbl...
> Last night out Exchange server (2003) blew up, literally. The only things
we
> have for a backup is a clean Windows 2003 standard edition ghost image and
> the information store and logs (full backup) from the night before. when i
> run the disasterrecovery switch is tells me to go to the control panel i
> assume to reinstall it? the long and short is, how will installing
exchange
> on the server (exactly the same) affect the configuration stored in active
> directory?
> -gm
>
>

Veets
03-24-04, 09:19 AM
something
Care to share?
Veets

"Gabe Matteson" <gmatteson@nospam.cox.net> wrote in message
news:%23fZuCRQEEHA.2988@TK2MSFTNGP12.phx.gbl...
> Resovled -
>
> "Gabe Matteson" <gmatteson@nospam.cox.net> wrote in message
> news:eEmQ6UPEEHA.3568@tk2msftngp13.phx.gbl...
things[color=blue]
> we
and[color=blue]
i[color=blue]
> exchange
active[color=blue]
>
>

Gabe Matteson
03-25-04, 12:22 PM
something
I ghosted the new exchange server with a generic 2003 standard image,
applied my virus scanning software and had SUS configured to push all the
latest updates to it. rebooted, applied to static ip, then ran the exchange
setup with the disasterrecovery switch which is essence pulls the exchange
configuration from AD and apply it to the installation. applied the security
hotfix, rebooted, waited 15min rebooted again just to make sure everything
was syncd with AD then went in and mounted my message stores which were on
another raid 5 set and the log files were on a raid 1 set. done! took a max
of about 40minutes :) i never had a recovery go so smooth
-gm
"Veets" <dddetrretsssadasy@hotnospmamail.com> wrote in message
news:e1GN1SaEEHA.3256@TK2MSFTNGP09.phx.gbl...
> Care to share?
> Veets
>
> "Gabe Matteson" <gmatteson@nospam.cox.net> wrote in message
> news:%23fZuCRQEEHA.2988@TK2MSFTNGP12.phx.gbl...
> things
> and
when[color=blue]
> i
i[color=blue]
> active
>
>

vBulletin v3.6.2, Copyright ©2000-2010, Jelsoft Enterprises Ltd.