NZ university automates virtual machine backup

By Simon Sharwood
Friday, 13 February, 2009


Auckland University will be upgrade its disaster recovery (DR) regime so that copies of 800-plus virtual machines will be automatically transferred between its main data centre and its DR site.

The University plans this new level of protection as part of the evolution of its DR plan, which was initiated in 2005, when System Architect John Askew says “we were given a challenge implement a full DR program with the ability to recover all core systems in four hours.”
“At the end of 2004, we did a business continuity review with the auditors and one thing that came out of it is that Universities are considered a place of learning and it was felt we could carry on teaching without IT.”

But the review reached a different conclusion. “Without IT, we cannot operate the business,” Askew says. “You could not actually do it. With no network and no authentication we cannot teach.”

The new DR site went live in 2007, but during the time taken to implement the new facility the University had started to make extensive use of virtualisation for servers and storage.

“We wanted to copy virtual machines and the data they rely on to the remote site,” Askew says. A method of doing so was devised, but required manual intervention. With virtual machines proliferating and disaster recovery processes becoming more complicated, the University decided to automate its processes.

“One of the great caveats of DR is that you plan for none of your people to be left standing so anyone can restore operations,” Askew says. “With a manual system that gets harder. That’s why we wanted an automated process to integrate storage and virtual machines. It was the next logical step.”

The University is now working on automated tools that use VMware Site Recovery Manager to copy virtual machines to its DR site whenever they are altered. “They’ll all be sitting there in standby mode,” Askew says. In the event of a disaster, the images of these virtual servers will automatically be installed on the server farm at the DR site, supplanting any of the test and development activity the site conducts when not performing its main function.

“Our recovery time objective is less than four hours,” Askew says. “We’ve tested it and done it in two.”

Related Articles

Storage strategy in the multicloud era

Data has become the essential raw material in the strategic orientation of business, making data...

Private AI models: redefining data privacy and customisation

Private AI signifies a critical step forward towards a more secure, personalised and efficient...

Why having an observability strategy is critical for effective AI adoption

As organisations continue to adopt AI and put it to work in a variety of innovative ways, many...


  • All content Copyright © 2024 Westwick-Farrow Pty Ltd