The solution was designed for chief technology officers who don't want the expense and headache of creating an in-house disaster recovery solution, yet must plan for and survive catastrophic events. Those businesses without a disaster recovery plan in place are at risk of business failure, if their company experiences a disaster.
"To keep costs low, Teradata customers can tailor the level of assistance needed to meet the specific demands of their enterprise, and also have access to the Teradata Recovery Centers 24 hours a day, 365 days a year," said Randy Lea, vice president, products and services marketing, Teradata. "Customers bring knowledge of their data and applications and Teradata brings the expertise and experience in disaster recovery. Working together, we can help a customer build a better and less expensive disaster recovery solution than what they can build on their own."
The experienced Teradata team, who conduct multiple simulations monthly, understands data warehouse best practices. They provide guidance on developing and updating comprehensive recovery plans, training, and yearly testing. To simplify the process for chief technology officers, the Teradata solution offers customers an off-site, dedicated, secured facility that is complete with equipment, software licenses, and database administrators experienced in disaster recovery. It includes all the costs for cooling, powering, and maintaining the data warehouses. This shared resource business model lowers the cost of disaster recovery below what customers can achieve on their own, with their own dedicated servers and staff.
Lea commented that, "Customers have the opportunity to practice their procedures every year in the Teradata recovery center by simulating a disaster, whether an extreme disaster or inconvenient interruption. It is often surprising what customers discover during their practice sessions - it is better to discover vulnerabilities during testing rather than during a true disaster. During their yearly test, one customer found that the addresses of key servers had changed since their last disaster recovery test, which caused hours of delay in the practice recovery process. If this had been a real disaster, the incorrect server addresses could have turned the delay of hours into a delay of days potentially shutting down the business. The customer was able to update their recovery plan to include change control procedures, which will prevent the problem from happening."