27.02.2013 Views

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Understanding registry synchronization resources<br />

History Files Store Folder: Folder to keep the writing requests to the remote disk<br />

in files<br />

Kernel Queue Size: Size to keep the writing request to the remote disk in<br />

the kernel space memory<br />

Application Queue Size: Size to keep the writing request to the remote disk in<br />

the user space memory<br />

Thread Timeout: Timeout when it became unable to transfer data <strong>for</strong>m<br />

the kernel queue to the application queue<br />

Max. size of history file size (MB): Upper limit of amount of files stored in history files<br />

store folder.<br />

Upper Bound of Communication Band (KB/sec.):<br />

Upper limit of communication band on Mirror<br />

Connect.<br />

Understanding registry synchronization resources<br />

Dependencies of registry synchronization resources<br />

By default, this function depends on the following group resource types.<br />

Group resource type<br />

Floating IP resource<br />

Virtual IP resource<br />

Virtual computer name resource<br />

Disk resource<br />

Mirror disk resource<br />

Hybrid disk resource<br />

Print spooler resource<br />

Registry synchronization resources<br />

Registry<br />

server1 failed<br />

server1 server2<br />

Failover<br />

Registry<br />

server1 server2<br />

Registry keys to be synchronized at failover can be configured. When the content in a registry<br />

key set as synchronization target is updated while registry synchronization resource is active, the<br />

updated content is reflected to the registry of the Failover Target Server.<br />

The following describes how a registry synchronization resource synchronizes registry:<br />

3. When there is a registry synchronization resource in a failover group, update of a registry<br />

key that has been configured is monitored when the registry synchronization resource is<br />

activated.<br />

4. When the registry key update is detected, what is in the registry key is saved as a file in the<br />

local disk. Then the file is delivered to each Failover Target Server.<br />

5. The servers that received the file keep it in their local disks. If a failover occurs and registry<br />

synchronization resource is activated in a server that received the file, the content of the file<br />

is restored in the corresponding registry key.<br />

Section II Resource details<br />

459

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!