Business Considerations
1. Risk Assessment:
- Identify potential risks and threats to the business, considering natural disasters, cyberattacks, human errors, and other possible incidents.
2. Data Classification and Prioritization:
- Classify and prioritize data based on its importance to the business.
- Determine the maximum acceptable downtime for each critical function.
- As a part of Veeam Recovery Orchestrator configuration we will want to know what critical workloads need to be protected and recovered.
- We also need to know how these interdependent workloads need to be group during the recovery orchestration.
3. Recovery Locations:
- Assess the existing technology infrastructure to which locations are best suited for restoration of this data.
- Select appropriate technologies, such as, hardware, networking, and cloud services.
4. Recovery Time Objective (RTO) and Recovery Point Objective (RPO):
- Define specific RTO and RPO metrics for each critical business function.
- RTO is the maximum time it takes to restore a system after a disruption, while RPO is the acceptable data loss in a disaster.
5. Testing and Validation:
- Develop a testing plan to regularly validate the effectiveness of the disaster recovery solution.
- Conduct simulated disaster scenarios to ensure that the recovery process meets the defined objectives.
6. Scalability and Flexibility:
- Design the DR solution to be scalable, accommodating the organization's growth and evolving technology requirements.
- Ensure flexibility to adapt to changes in business processes and technology.
7. Security Measures:
- Implement robust security measures to protect the DR infrastructure from potential cyberthreats.
- Consider encryption, access controls, and other security best practices.
8. Documentation and Training:
- Document the disaster recovery plan comprehensively, including procedures, contact information, and technical details.
- Provide training for employees involved in the DR process to ensure a coordinated and effective response.
9. Regulatory Compliance:
- Ensure that the disaster recovery solution aligns with relevant industry regulations and compliance standards.
- Regularly review and update the DR plan to maintain compliance with changing regulations.
10. Communication Plan:
- Develop a communication plan to keep stakeholders informed during a disaster.
- Establish communication channels and protocols for notifying employees, customers, and other key stakeholders.
11. Continuous Improvement:
- Implement a process for continuous improvement, regularly reviewing and updating the disaster recovery solution to address emerging threats and technology changes.
Deployment Considerations
Review the outlined sections as a deployment checklist in order to understand typical deployment scenarios for Veeam Recovery Orchestrator, as well as placement best practices. You are encouraged to read further into the attached guides for more specifics on server requirements.
Placement
- The Veeam Recovery Orchestrator server should not be deployed at the protected site. It should be deployed on a witness or DR location to be available during a Disaster Recovery scenario.
- We also recommend the Veeam Backup & Replication server is placed at a DR or Witness location, as the core functionality of Replication & Failover is managed on this server.
- Orchestrator simply orchestrates these tasks with additional automation and enhanced capabilities.
- Veeam Backup & Replication server can be migrated. Continue reading in the User Guide.
Sizing
- Most importantly the sizing of the server is based on the number of orchestrated systems. Find detailed requirements and hardware recommendations in the User Guide.
Licensing
It’s important to understand what licensing and how licensing can be used with Veeam Recovery Orchestrator:
- This article describes how the managed objects are licensed, and what types of licenses you will need to obtain.
- Due to enhanced integrations and architectural changes across the Veeam Data Platform, there are new license requirements for Veeam Recovery Orchestrator v7
SQL Server and Veeam ONE
- Local or Remote installation of SQL server.
- Since Veeam Recovery Orchestrator leverages Veeam ONE, for large enterprise environments you may want to consider an external SQL server.
- Veeam ONE Database Calculator for large environments
Veeam Recovery Orchestrator pre-requisite considerations
On top of the sizing aspects we mentioned above you will also want to considers Roles, Permissions and Port requirements.
Veeam Recovery Orchestrator system requirements
The machine where Orchestrator will be deployed must meet the necessary hardware and software requirements.
Deployment Scenarios
Orchestrator supports a number of deployment scenarios. This article describes 4 common scenarios. You can also combine any of the described scenarios to support your own data protection strategy.
Infrastructure Deployment
Deployment Checklist
Deploy the Virtual/Physical servers that the Veeam Recovery Orchestrator solution will be hosted on. Refer to the previous sections for the requirements for these servers.
Refer to the User Guide that outlines the Ports and Firewall exceptions that are required for the Veeam ONE solution to communicate with other third-party components in your ecosystem.
Important: Veeam Recovery Orchestrator Services can only be installed on a domain machine.
If you need more help getting started, you can post your question in the comments section below or contact us at any time and someone from the Customer Success team will be there to assist you.