Windows boot without event log. Setting up LUNs for DR replication

Hello,
We are setting up SAN to SAN replication between 2 offices for Disaster Recovery.  The replication looks at block level changes on each LUN.  The LUNs are all Windows 2003 virtual machines.  In order to reduce the amount of changes being replicated, we want to move the Windows Event logs to a disk on a LUN that is not replicated.  If we go to the DR SAN where that LUN with the event logs does not live, Will the Windows 2003 server be able to boot without its event log drive?  After we get it up, we can just point the event logs back to C:, but we dont want to replicate these changes on a daily basis.  We have all ready moved the pagefiles to a disk on nonreplicated LUN and that cut down the traffic greatly.  However, we are just trying to find ways to reduce replication traffic further.  Thanks.
delmarvamonkeyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TripyreCommented:

A: On a Server 2003 machine, the event log files are, by default, located in the %WinDir%\System32\Config folder. On a Server 2008 machine, they default to the folder %WinDir%\System32\Winevt\Logs.
To relocate the event log files on Server 2003, you must modify the file system path stored in the "File" registry value. You can find this value in the registry key HKLM \SYSTEM\CurrentControlSet\Services\Eventlog\<EventLogName>. The <EventLogName> placeholder represents the name of the log for which you want to configure a different location—it can be the Application, System, or Security log. To apply the change, you must restart the computer.
In Server 2008, you can relocate the event log files from the Server Manager console. To do so, start Server Manager and expand Diagnostics/Event Viewer/Windows Logs in the console tree. Right-click the log for which you want to change the location and click Properties. Type the new file system location for the event log in the Log path box and click OK.
The Server should boot if the logs are not available as this is for historical purposes only and not required.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
delmarvamonkeyAuthor Commented:
I forgot to add we have the "Shut down system immediately if unable to log security events"  Could that be an issue?
0
TripyreCommented:
Not sure, never used that configuration before.  Not sure if windows would set the logs to c: drive after the fact.
0
delmarvamonkeyAuthor Commented:
Ok, well I can always bring up a test VM and verify this behavior.  Thanks for the input.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Disaster Recovery

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.