Protecting Data Stored On Premises and in Azure Using NetVault
as described in the NetVault Overview section). The data is restored to NetVault Client
2. The benefit of this scenario is that NetVault Client 2 can be physically located in a
different, on-premises location, which is ideally suited for a disaster recovery scenario.
SCENARIO 2: BACK UP ON PREMISES APPLICATIONS AND DATA AND
RESTORE TO THE CLOUD
Restore your data to a NetVault Client (Client 2) in the Azure cloud. The benefit here is
a more robust disaster recovery solution. With this added flexibility, the recovery target,
client 2, is deployed in the cloud and accessible from any location.
Azure Cloud
Customer on
premises network
NetVault client 1
Virtual tape
library
NetVault
Server
Virtual network
gateway
NetVault SmartDisk
or QoreStor
Backup data and
control messages
VPN
gateway
NetVault client 2
Restore data and
control messages
NetVault Server - NetVault
Client control messages
Scenario 2: Backing up on-premises applications and data, and restoring to the cloud,
using NetVault.
SCENARIO 3: BACK UP AND RESTORE
APPLICATIONS AND DATA IN THE CLOUD
This scenario describes a NetVault domain that is completely contained in the Microsoft
Azure cloud. In this scenario, two NetVault Clients (which may be file servers or
application servers) are deployed in the cloud.
Azure Cloud
Virtual tape
library
NetVault
Server
NetVault client 1
NetVault client 2
NetVault SmartDisk
or QoreStor
Backup data and
control messages
Restore data and
control messages
NetVault Server - NetVault
Client control messages
Scenario 3: Backing up and restoring applications and data in the Azure cloud
using NetVault.
3
The scenarios described
here will help you
develop a Microsoft
Azure-based data
protection strategy
with NetVault.
NetVault ensures the
protection of businesscritical applications
and data like that
stored in Office365
Exchange Online.
The data on NetVault Client 1 is configured to be backed up by the NetVault Server
to multiple backup storage targets, also in the Azure cloud. These are either a VTL,
NetVault SmartDisk or optionally, Quest QoreStor. The size, type and frequency of the
backup policy drives what the optimal storage target configuration should be.
It’s also configured to restore the data from NetVault Client 1 to NetVault Client 2. Uses
of this scenario include moving data from one server to another newer configuration, as
well as for cloning of systems.
SCENARIO 4: AZURE-BASED OFFICE 365 PROTECTION
Microsoft Office 365 enables enterprise customers to work anywhere, anytime, without
the need to host their own email infrastructure. But there is a catch.
With Office 365, it is your data – you control it and it is your responsibility to protect it.
Office 365 does not provide a true backup. For example, emails older than 30 days are
not backed up. This leaves you at risk of data loss due to various causes – human error,
ransomware attacks, etc.
NetVault provides a plug-in specifically designed for Office 365. This plug-in lets
you create flexible backup policies that can account for multiple recovery scenarios.
Through a web-based user interface and automated workflow process, the plug-in
offers a centralized way to set up, configure, and define backup and restore policies for
Office 365.
Through integration with a range of backup devices – such as NetVault SmartDisk or
Quest QoreStor as shown in Figure 4, your data is protected and stored offsite to meet
your disaster-recovery and business-continuity goals. The Office 365 plug-in is based
on the Microsoft Graph API and is extremely scalable.
NetVault server
Browser
NetVault client
HTTP(S)
User
NetVault UI
Job manager
NetVault
messaging
Media manager
NetVault Plug-In
for Office365
CLR
Graph library
DR site
Azure Cloud
Office 365
NetVault SmartDisk
or QoreStor
Exchange
Online
Scenario 4: Azure-based Office 365 protection using NetVault.
4
REST call
JSON object
Please complete the form to gain access to this content
