<div>
I forgot to add we have the &quot;Shut down system immediately if unable to log security events&quot; &nbsp;Could that be an issue?
</div>


I forgot to add we have the "Shut down system immediately if unable to log security events"  Could that be an issue?

<div>
Not sure, never used that configuration before. &nbsp;Not sure if windows would set the logs to c: drive after the fact.<br />

</div>


Not sure, never used that configuration before.  Not sure if windows would set the logs to c: drive after the fact.


<div>
Ok, well I can always bring up a test VM and verify this behavior. &nbsp;Thanks for the input.
</div>


Ok, well I can always bring up a test VM and verify this behavior.  Thanks for the input.

<div>
<div class="content wysiwyg-content">
Hello,<br />
We are setting up SAN to SAN replication between 2 offices for Disaster Recovery. &nbsp;The replication looks at block level changes on each LUN. &nbsp;The LUNs are all Windows 2003 virtual machines. &nbsp;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. &nbsp;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? &nbsp;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. &nbsp;We have all ready moved the pagefiles to a disk on nonreplicated LUN and that cut down the traffic greatly. &nbsp;However, we are just trying to find ways to reduce replication traffic further. &nbsp;Thanks.
</div>
</div>


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.

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

Disaster Recovery is the planning for and creation of policies and procedures related to the resumption or continuation of an organization's functions following a catastrophic event. The term is most frequently used in relation to failure of networks, but DR preparations also include other business systems and personnel considerations.

Disaster Recovery

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Computer data storage, often called storage or memory, is a technology consisting of computer components and recording media used to retain digital data. In addition to local storage devices like CD and DVD readers, hard drives and flash drives, solid state drives can hold enormous amounts of data in a very small device. Cloud services and other new forms of remote storage also add to the capacity of devices and their ability to access more data without building additional data storage into a device.