Article

(View Disclaimer)

It's a good bet that disaster recovery planning is always on your mind, but not always at the top of your To-do list. Like it or not, it is an essential task for any data center manager. From crazy weather, to accidents, to disgruntled employees, you need to plan for the unpredictable, or risk a catastrophic blow to your organization.

Don't miss this free webcast series which explores several facets of effective disaster recovery planning.

July 12 -- Part 1: New Platforms, New Technologies, Old Headaches
In this session you'll learn:

• Mixed Platforms are becoming the norm in most data centers– Windows, Linux, and OES2. Don’t built separate DR silos for each
• Heterogeneous environments can create overhead and management challenges
• Use virtualization as a simple solution to protect physical, virtual, Windows, Linux, OES2

August 9 -- Part 2: Update your Disaster Recovery Plans with Virtualization
In this session you'll learn:

• Why it's expensive to manage physical data environments
• How virtualization and consolidated recovery can reduce costs
• How virtualization can remove management barriers and reduce recovery time

September 13 -- Part 3: Disaster Recovery and the Cloud
In this session you'll learn:

• Public vs. Private vs. Hybrid — Why it matters and how it can effect disaster recovery
• How virtualization is the stepping stone to the cloud
• How to leverage virtualization to reduce the cost and improve the performance of your disaster recovery today

October 18 -- Part 4: Disaster Recovery Planning and the Real Cost of Downtime
In this session you'll learn:

• Why business tolerance for risk is becoming lower and lower
• Why traditional disaster recovery testing is a painful and time-consuming process
• How consolidated recovery can make disaster recovery testing easier and reduce the testing cycle and disruptions

Register here

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.