29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Operating system based clustering<br />

The <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> high availability framework provides<br />

integration into an environment that uses other high availability frameworks, such<br />

as operating system-based clustering software like HACMP on AIX, or parallel<br />

sysplex on z/OS, to provide high availability for resources for which <strong>WebSphere</strong><br />

does not provide specific high availability functions. Consider such a technique<br />

for <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> components such as a deployment manager,<br />

node agents, single server environments, and so on.<br />

5.1.2 Disaster recovery<br />

The main considerations in disaster recovery planning are how to bring up a fully<br />

operative environment after a disaster struck the system, how much data loss<br />

you can afford, and how can ensure that your data remains consistent.<br />

Cluster isolation 1 , for example, is a potential threat to your data consistency and<br />

must be avoided in all circumstances. After the data consistency issues are<br />

resolved (meaning that your problems regarding your <strong>WebSphere</strong> data, such as<br />

configuration repository, logs and so forth are also resolved) you can resume<br />

your planning for <strong>WebSphere</strong> disaster recovery.<br />

Note: A design approach to spread your <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> cell<br />

over multiple data centers is not a sufficient response to a disaster recovery<br />

design challenge. Refer to the developerWorks article Everything you always<br />

wanted to know about <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> but were afraid to ask --<br />

Part 2, available at the following Web site:<br />

http://www-128.ibm.com/developerworks/websphere/techjournal/0512_col<br />

_alcott/0512_col_alcott.html<br />

There is no common solution for <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> in a disaster<br />

recovery scenario as this depends on the existing environment, requirements,<br />

applications and budget. For some considerations on disaster recovery in your<br />

<strong>WebSphere</strong> environment, refer to the Developer works article Everything you<br />

always wanted to know about <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> but were afraid to<br />

ask, Part 5, available at the following Web page:<br />

http://www.ibm.com/developerworks/websphere/techjournal/0707_col_alcott<br />

/0707_col_alcott.html<br />

1 Cluster isolation in this context means a condition that each member of a clustered system<br />

considers the other to be gone and therefore taking over the service. The result would be to have<br />

two systems manipulating data.<br />

Chapter 5. Topologies 125

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

Saved successfully!

Ooh no, something went wrong!