Reliable Infrastructure.
Prepared for Disruption.
Explore the architecture behind NovaCore Systems' Virtual Desktop and Application Delivery solutions, including infrastructure availability, recovery objectives, and disaster recovery planning.
Explore Our ArchitectureUnderstanding the Infrastructure Behind Your Applications
Business applications are essential to daily operations. Understanding the infrastructure that delivers those applications, and how it responds to disruption is an important part of evaluating a Virtual Desktop and Application Delivery solution.
NovaCore Systems provides insight into the architecture, availability considerations, recovery objectives, and disaster recovery planning associated with its solutions. This information helps organizations evaluate how their application access requirements align with infrastructure capabilities and business continuity expectations.
Clear infrastructure. Defined objectives. Informed decisions. Technical transparency helps businesses assess their application delivery environment.
How NovaCore Connect Works
An overview of how users access desktops and applications through the NovaCore Connect environment hosted on AWS.
User Access
HALB
High Availability Load Balancing
Gateway
Secure access to desktops and published applications
Desktop & Application Delivery
AWS Infrastructure
Conceptual architecture illustrating the relationship between user access, connection services, desktop and application delivery, and supporting AWS infrastructure. Actual configurations may vary.
Infrastructure Designed for Reliable Application Access
NovaCore Connect is supported by cloud infrastructure designed to provide dependable access to virtual desktops and applications while supporting availability, recovery, and business continuity requirements.
Compute Resources
AWS EC2 compute resources provide the processing capacity required for virtual desktops, published applications, and supporting application delivery services.
Directory Services
Active Directory provides centralized identity and authentication services, helping control access to desktops, applications, and supporting resources.
Shared Storage
Amazon FSx provides managed file storage for workloads that require shared access to files and application data within the environment.
Availability Considerations
Infrastructure planning considers service dependencies, resource availability, recovery requirements, and the ability to restore critical services following an interruption.
Understanding RTO & RPO
Effective recovery planning starts with understanding how quickly critical services must be restored and how much data an organization can afford to lose following a disruption.
Recovery Time Objective
How quickly must services be restored?
RTO defines the target time for restoring access to critical desktops, applications, and supporting infrastructure after an interruption.
Planning Consideration
Establish acceptable downtime for business-critical applications and determine the recovery steps needed to meet that target.
Recovery Point Objective
How much data loss is acceptable?
RPO defines the maximum acceptable period of data loss measured backward from a disruption. It helps guide data protection, backup frequency, and recovery planning.
Planning Consideration
Determine how frequently critical data must be protected to support the organization's recovery requirements.
Recovery Objectives Are Business-Driven
RTO and RPO targets depend on business requirements, application dependencies, data protection arrangements, and the recovery capabilities implemented for each environment. These objectives should reflect an organization's operational priorities.
Preparing Your Infrastructure for Recovery
Business continuity depends on a clear strategy for restoring critical infrastructure, applications, and data when unexpected disruptions occur. NovaCore Systems incorporates backup protection and recovery planning into its infrastructure approach.
Veeam Backup & Replication
Veeam Backup & Replication is the planned technology for protecting supported infrastructure workloads and providing recovery capabilities when systems experience an outage or failure.
The backup and recovery design will account for workload requirements, backup frequency, retention policies, storage, and the resources needed to restore critical services.
Protect critical infrastructure and workloads.
Establish restoration priorities and dependencies.
Plan the recovery of protected systems and services.
Recovery Process
Establishing Recovery Objectives
Recovery objectives help define the expected timeframe for restoring services and the acceptable amount of data loss.
Recovery Time Objective
Defines the target timeframe for restoring critical infrastructure and applications following a disruption.
Recovery Point Objective
Defines the maximum acceptable amount of data loss measured in time, helping determine backup frequency.
Infrastructure Recovery Priorities
Recovery planning considers the infrastructure components required to restore virtual desktop and application delivery environments.
Core Infrastructure
Account for directory services, DNS, networking, compute and storage dependencies required for service delivery.
Desktop & Application Delivery
Prioritize the recovery of virtual desktop environments, application delivery services, gateways and supporting systems.
Service Restoration
Define restoration procedures and the sequence for bringing critical infrastructure and business services back online.
Recovery Verification
Establish procedures to verify system functionality, application access and data integrity following restoration.
Recovery capabilities and achievable RTO and RPO targets depend on the selected Veeam configuration, protected workloads, backup storage, recovery infrastructure and documented business requirements. Backup and replication do not independently guarantee uninterrupted service or a specific recovery timeframe.
Validate Recovery Before It Is Needed
A recovery plan needs to be validated, not just documented. Disaster recovery testing helps determine whether protected data can be restored, critical services can be recovered, and documented procedures support business continuity objectives.
Backup Verification
Review backup status, retention settings, and protection coverage to identify gaps before recovery is required.
Restore Testing
Test the restoration of selected data, workloads, or systems in an appropriate environment to validate recoverability.
Service Validation
Confirm that restored systems, directory services, storage, desktops, and applications function as expected for the scope of each test.
Results & Improvements
Document test results, recovery times, issues, and corrective actions. Update procedures as infrastructure and business requirements change.
Testing frequency, scope, and procedures should be defined according to business requirements, recovery objectives, and the implemented backup and recovery configuration. Test results should be documented and reviewed to guide ongoing improvements.
Download the Infrastructure and Business Continuity
Download PDFGet A Free Consultation
Speak with a Technology Expert
- A NovaCore Systems expert will contact you to discuss your company.
- We’ll discuss your goals, challenges, software, and technology.
- We’ll recommend solutions to help you reach your goals.
- If we sound like a good fit, we will prepare a customized proposal within one business hours.
