Veeam with HPE
StoreOnce Catalyst
Configuration Guide
Veeam with HPE StoreOnce Catalyst Configuration Guide
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Software, hardware and security requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Creating an IP-based Catalyst Store for Veeam Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Configuring Catalyst Store Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuring a FC StoreOnce Catalyst Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Initial FC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Creating a Veeam Backup Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Creating a Veeam Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Veeam with HPE StoreOnce Catalyst for vPower Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Copying Veeam backups to a remote site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Architecture "A" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Architecture "B" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Implementation steps for copying Veeam backups to a remote site . . . . . . . . . . . . . . . . . . . . . . 21
Architecture "A" configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Architecture "B" configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Architecture “B” restore configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Utilizing backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
About Veeam Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
© 2016 Veeam Software
2
Veeam with HPE StoreOnce Catalyst Configuration Guide
Introduction
This guide is for users responsible for setting up and managing data availability infrastructures that
include Veeam® Backup & Replication™ and HPE StoreOnce Catalyst. It assumes the reader is familiar
with Veeam Backup & Replication and HPE StoreOnce backup appliances. Please refer to the
Veeam Backup & Replication User Guide for more detailed information. For information on HPE
StoreOnce appliances, please visit www.hpe.com/storage/StoreOnce.
Veeam Backup & Replication integrates the StoreOnce Catalyst client software to achieve sourceside deduplication and virtual synthetic full backups, leading to more efficient backup data transfer,
less network utilization and overall better performance in comparison to backup using traditional
NAS protocols (CIFS and NFS). This guide covers the setup and configuration of Veeam Backup &
Replication with HPE StoreOnce Catalyst for both on-site and off-site backup data retention. HPE
StoreOnce optimizes as an on-site and off-site backup repository with high-efficiency deduplication
and compression to minimize storage space consumption. The deduplication processing means the
read performance may not be high enough to support some vPower NFS features. The guide describes
an alternative solution for these, with backups written first to regular disk storage, and then copied
to a StoreOnce appliance. The backups on a regular disk will support all vPower NFS operations. The
backup copies to the StoreOnce appliance minimize the storage consumed for longer retained backup
data and as a source to copy backup data to an off-site StoreOnce appliance. For off-site copies of
virtual machine (VM) backup data, two copy scenarios are compared; the first has a single local Veeam
gateway server and the second has a Veeam gateway server at the local and remote locations.
Software, hardware and security requirements
• Virtual or physical 64 bit Windows Server 2008 SP2 or newer with administrator credentials
• Veeam Backup & Replication v9 or later; Enterprise or Enterprise Plus Edition
• StoreOnce appliance with software version 3.13.1 or later
• 1 0 GbE or 8 Gb FC connectivity from the Veeam gateway server to the StoreOnce
appliance — recommended
• Administrator credentials to the HPE StoreOnce appliance
© 2016 Veeam Software
3
Veeam with HPE StoreOnce Catalyst Configuration Guide
Creating an IP-based Catalyst Store
for Veeam Backups
You must create a StoreOnce Catalyst store on your StoreOnce appliance to work with Veeam Backup &
Replication.
1. Log onto the HPE StoreOnce Management Console (StoreOnce GUI) with administrator privileges.
2. Navigate to HPE StoreOnce>StoreOnce Catalyst>Stores. Click Create.
3. C
hange the store details as appropriate. Find the table describing the store details in the “StoreOnce
Catalyst Stores page” section of the HPE StoreOnce Backup system user guide for your product.
4. It is also important to adjust the Primary and Secondary Transfer Policy to meet the intended usage
of this Catalyst Store:
• L ow Bandwidth/Low Bandwidth leverages StoreOnce Catalyst source-side deduplication and
is most effective when multiple virtual hard disks are backing up to a Catalyst store. This is the
preferred option for copying backups directly to remote StoreOnce appliances, and it will help
achieve the highest level of aggregated backup throughput, both on and off site
• H
igh Bandwidth/High Bandwidth disables StoreOnce Catalyst source-side deduplication,
as well as compression and inline Catalyst data checksum. This is typically recommended for
Catalyst stores that won’t have multiple write streams — for example, backup jobs with single
large VMs that have one or two virtual hard disks. This policy should not be used without 10 GbE
or 8 Gb FC connectivity
5. The store will appear in the top panel. This means the HPE StoreOnce Backup system is configured
and ready to accept backups.
© 2016 Veeam Software
4
Veeam with HPE StoreOnce Catalyst Configuration Guide
Configuring Catalyst Store Access Control
In setting client access control, two modes can be set on StoreOnce Catalyst stores:
• No Client Access Permission Checking allows all clients to have access to the StoreOnce Catalyst store
• C
lient Access Permission Checking allows a select group of client identifiers to access to the
StoreOnce Catalyst store. To enable this mode, enable Client Access Permission Checking on the
Settings tab of the StoreOnce GUI. To access this tab, navigate to HPE StoreOnce>StoreOnce
Catalyst>Settings. Also, an individual StoreOnce Catalyst store must grant access for a client
identifier within the Permissions tab of a StoreOnce Catalyst store
When using Client Access Permission Checking, access to StoreOnce Catalyst stores is controlled through
client identifiers. For Veeam Backup & Replication, the client identifier is Veeam, which is the client name
to use when creating the client entry under Client Access Permission Checking, along with a user-defined
password. These credentials will be used in the Backup Repository creation wizard.
Configuring a FC StoreOnce Catalyst Store
StoreOnce Catalyst over Fibre Channel functions the same way as standard StoreOnce Catalyst (over
Ethernet); Veeam will not perceive a difference. However, some configuration is required to set up the
backup and restore connections between the ports on the HPE StoreOnce Backup system and the
ports on the client servers. This is done using the Fibre Channel Settings tab which is available within
the StoreOnce GUI only if StoreOnce Catalyst over Fibre Channel is enabled.
© 2016 Veeam Software
5
Veeam with HPE StoreOnce Catalyst Configuration Guide
Prerequisites
• The Veeam gateway server and the HPE StoreOnce appliance are connected to the Fibre Channel network.
• V
eeam servers can communicate with the HPE StoreOnce appliance over a Fibre Channel network.
To do so, the storage administrator must ensure that any network segregation, such as zoning, is set
up to handle required connectivity between the server and appliance.
Note: When using StoreOnce Catalyst over Fibre Channel administrator privileges are required to accesses
OS-specific device files associated with StoreOnce Catalyst over Fibre Channel devices. Fibre Channel users
are advised to consult the Data Agile Backup, Recovery and Archive (BURA) Compatibility Matrix (available at
www.hpe.com) to ensure that client host bus adapters (HBAs), switches, Fibre Channel driver, and firmware
versions are supported.
Initial FC configuration
Navigate to HPE StoreOnce>StoreOnce Catalyst>Fibre Channel Settings and locate the identifier
at the top of the screen. This is the Fibre Channel address of the StoreOnce and is used to identify the
StoreOnce Backup system in Veeam. It is in the format COFC-<device-id>; you may provide an identifier
alias to make it easier to identify from Veeam. This Catalyst over Fibre Channel identifier is provided to
Veeam where an Ethernet address would otherwise be provided.
1. HPE recommends the default values in the target ports section. However, you can edit the speed.
2. L ocate the world wide port name for each port on the StoreOnce Backup system. This is the
information needed to connect the catalyst client integrated in Veeam with the StoreOnce Backup
system. Use this information to zone your client Fibre Channel ports with your StoreOnce Fibre
Channel ports.
3. L ocate the number of logins and devices per initiator port for each port. These values determine the
number of concurrent backup and restore connections allowed on each Fibre Channel port on the
HPE StoreOnce Backup system.
• N
umber of logins defines the number of client-side ports that are zoned to connect to that
port on the StoreOnce Backup system and cannot be edited
• D
evices per initiator port determines the number of backup and restore connections that are
allowed for each client login to that port on the StoreOnce Backup system. This value should
be increased if multiple concurrent backup streams are required. The maximum allowed is 64
devices per login. If this value is increased, a device file rescan on the client is needed before the
change is recognized
Note: The number of devices per initiator port should be increased when multiple backup streams are
required so that multiple LUNs are presented to the client.
© 2016 Veeam Software
6
Veeam with HPE StoreOnce Catalyst Configuration Guide
The number of paths available to a particular client is calculated as number of client ports zoned x
number of StoreOnce node ports zoned x devices per initiator port
Table: Example relationships between device per initiator port and number of connections on
Windows and HP-UX
Client-side
HPE StoreOnce
Devices per
initiator port
Number of concurrent backup and
restore session (per service set)
1 port zoned to
4 ports
1
4
2 ports zoned to
4 ports
1
8
2 ports zoned to
2 ports
4
16
2 ports zoned to
4 ports
8
64
Note: The number of StoreOnce Catalyst over Fibre Channel devices available must be at least one more than the
number of streams if the backup application or plug-in can open command sessions during a backup or restore.
Client Considerations for Windows — Administrator permissions are required to run catalyst over
Fibre Channel backups. StoreOnce Catalyst over Fibre Channel presents a device type of “Processor.”
These devices are shown as “Other Devices” in Windows Device Manager. After zoning the devices
or changing the number of devices per initiator port, right-click “Other Devices” and select “Scan for
hardware changes” to detect the new devices.
© 2016 Veeam Software
7
Veeam with HPE StoreOnce Catalyst Configuration Guide
Creating a Veeam Backup Repository
Backup repositories are simply defined as storage for Veeam backup files in Veeam Backup &
Replication. A backup repository receives its data from the Veeam Backup Proxy where data is read
and compressed before being sent to a gateway server, and then the StoreOnce. To create a Catalystenabled Veeam backup repository use the following steps:
1. Click on “Backup Infrastructure” in Veeam Backup & Replication.
2. Right click on “Backup Repositories” and choose “Add Backup Repository.”
3. Repository name — Give the repository a friendly name.
4. Repository type — Choose Deduplicating storage appliance.
© 2016 Veeam Software
8
Veeam with HPE StoreOnce Catalyst Configuration Guide
5. Deduplicating storage type — Choose HPE StoreOnce.
6. Server name — Enter the DNS name, IP address or choose Fibre Channel connectivity, along with
credentials to access the Catalyst Stores. If “Client Credential Check-in” has been configured as stated
above, you will use Veeam as the username and the password created in the client details under
HPE StoreOnce>StoreOnce Catalyst>Clients.
© 2016 Veeam Software
9
Veeam with HPE StoreOnce Catalyst Configuration Guide
7. Gateway server — The Veeam Backup & Replication architecture consists of two data mover
services — one on the source proxy and one on the backup repository. In the case of StoreOnce
where Veeam is unable to install this component directly on the storage system, Veeam leverages a
gateway server to host the data mover. The gateway server sits in front of the StoreOnce appliance
and integrates the StoreOnce Catalyst client, which is automatically installed when creating the
backup repository. This allows for source-side deduplication and advanced management of Veeam
backup files. The automatic selection option allows Veeam to choose any Windows server added
to Veeam Backup & Replication with access to the StoreOnce as a gateway server. If no additional
Windows Servers are added, Veeam will use the default backup proxy for this role. To ensure that
only servers capable of serving this role are used, it recommended that you explicitly select a
gateway server. This is a requirement if you are using FC connectivity and the chosen server must be
connected to the SAN fabric.
Note: Whenever possible we suggest configuring both proxy and gateway services to run on the same server.
This eliminates an extra hop for backup traffic and reduces backup proxy CPU utilization.
Note: When using virtualized Veeam components in vSphere, ensure that the vNIC is set to VMXNET3 rather
than the default E1000. This is particularly important for 10 GbE LAN.
8. Catalyst store — Select the store to be used with this Veeam backup repository.
Note: Advanced settings do not need to be adjusted for StoreOnce repositories.
© 2016 Veeam Software
10
Veeam with HPE StoreOnce Catalyst Configuration Guide
9. Concurrent tasks — Use this field to keep the overall number of concurrent streams to StoreOnce
below the maximum recommended for each appliance model. This information is reported in the
"Key Parameters" chapter in the "User Guide" specific for your StoreOnce model available at the
following link: HPE StoreOnce Backup
Note: It is possible to configure multiple Veeam backup repositories pointing to the same catalyst store. Each
backup repository can have different "Load Control" limits. This gives more flexibility for defining quality of
service rules.
10.Mount server — Mount servers perform the task of mounting backup files for various restores. For
on-site StoreOnce repositories, this can be left using the pre-filled server (the Veeam backup server),
however, it is recommended that you choose a Windows based server local for remote sites where
restores may be performed. This could also be the gateway server.
• vPower NFS — When a Veeam Instant VM Recovery™ is performed, backups are mounted to
the hypervisor and powered on in a read-only state. All new data will be written to a temporary
cache stored at the path specified on this page by default. It is best practice to have at least 15%
of the of the largest VM that could be recovered available at the specified path. For example, a
100 GB VM that may be restored should have 15 GB of free space on this location.
Note: Advanced repository settings should not be changed for StoreOnce Catalyst repositories.
© 2016 Veeam Software
11
Veeam with HPE StoreOnce Catalyst Configuration Guide
11.Review all settings and click finish.
© 2016 Veeam Software
12
Veeam with HPE StoreOnce Catalyst Configuration Guide
Creating a Veeam Backup Job
A Veeam backup job acts as a policy for protecting one or more VMs. A backup job holds specific
settings for compression, deduplication, transmission block size and application quiescence, in addition
to policies for backup file handling. This section will review the recommended settings when creating a
backup job targeting an HPE StoreOnce repository that is Catalyst enabled.
1. Click on Backup & Replication in the left-hand menu bar.
2. Right-click on “Backup” and choose “Backup.”
3. Give the job a friendly name.
© 2016 Veeam Software
13
Veeam with HPE StoreOnce Catalyst Configuration Guide
4. Choose “Add” and select the VM(s) you would like protected with this job.
Note: If a hierarchy object such as “Resource Pool” or “Cluster” is chosen, Veeam will backup all VMs under this
object. Also, new VMs added under the object will be backed up on subsequent backup job runs, or removed
from the job if they are removed from under the hierarchy object in the infrastructure.
5. Backup proxy — You can take advantage of Veeam’s intelligent load balancing between multiple
backup proxies by leaving this as “Automatic.” In the case of HPE StoreOnce, it is recommended that
your backup proxy be the same as your gateway server whenever possible. This will reduce the
number of “hops” in the data path and can reduce CPU utilization on the backup proxy.
6. Backup repository — Choose the repository created earlier in this guide.
© 2016 Veeam Software
14
Veeam with HPE StoreOnce Catalyst Configuration Guide
7. Retention policy — Retention is based on points in time correlating to the schedule of the job,
which will be covered in a couple of steps.
8. Advanced settings — For StoreOnce Catalyst repositories, the following settings are
recommended. If different settings are selected, a notification will appear asking if you would like to
change them automatically.
• Backup Tab
• Backup mode — Incremental
• S ynthetic full backups — Synthetic full backups provide new “checkpoints” for backup chains by
rolling up existing full and incremental backups to create new full backup files. HPE StoreOnce
Catalyst virtualizes this process on the StoreOnce appliance for reduced strain on backup
components and networks, and improves overall performance of the operation drastically
• Storage Tab
• Data deduplication — Disabled
• Compression level — Optimal
• Storage optimization — Local target (16 TB + backup files)
Note: It is required that you have at least one full backup for every seven incremental backups.
© 2016 Veeam Software
15
Veeam with HPE StoreOnce Catalyst Configuration Guide
9. Guest Processing — Guest processing enables transaction consistency for VM backups, indexing of
VM guest file systems for quick searching through the optional Veeam Enterprise Manager, and the
configuration of how logs of specific applications are handled. To enable these capabilities simply
check the appropriate box and supply administrator credentials. Additional details on configuration
of these features can be found in the Veeam Backup & Replication User Guide.
© 2016 Veeam Software
16
Veeam with HPE StoreOnce Catalyst Configuration Guide
10. Job scheduling — It’s recommended that you schedule daily backups for backup jobs targeting
StoreOnce repositories, thus limiting the number of incremental backups to maximum of seven
before a new synthetic full backup is created. If a better recovery point objective (RPO) is required,
you will be need to schedule more frequent synthetic full backups to meet this rule.
© 2016 Veeam Software
17
Veeam with HPE StoreOnce Catalyst Configuration Guide
Veeam with HPE StoreOnce Catalyst for
vPower Performance
To achieve the best possible performance of all Veeam vPower based features, such as Instant VM
Recovery, On Demand Sandbox™ and SureBackup®, a tiered architecture that consists of intermediary
non-deduplicating storage for short-term backup retention is recommended. This intermediary storage,
for example, can house a weeks-worth of backups that can be used for rapid restores of VMs living on
these most critical restore points, verification of backup file integrity, and a test/dev environment built
on backup files. An additional backup repository would be created for this. Other repository options
can include a SAN LUN, or a local or direct attached disk(s). Please use the Veeam Backup & Replication
User Guide for detailed instructions on setting up each of these other types of storage.
As Veeam backups land on the intermediary storage, Veeam backup copy jobs will be configured to copy
them over to HPE StoreOnce for long-term retention. Backup copy jobs will be covered in more detail later in
this guide as they are also used to move Veeam backup files from StoreOnce to StoreOnce.
© 2016 Veeam Software
18
Veeam with HPE StoreOnce Catalyst Configuration Guide
Copying Veeam backups to a remote site
Maintaining multiple copies of backups is critical to an organization’s data Availability strategy.
Veeam with HPE StoreOnce allows you to do this by making copies of Veeam backups that reside on
geographically separated HPE StoreOnce appliances. In the Veeam Backup & Replication v9, Catalyst
Copy is not used. There are two architectures currently supported using Veeam’s backup copy.
Architecture "A" — Site to site through source and target Veeam gateway servers
(Recommended).
Advantages
• Supports Veeam’s health check and heal functionality for backup files
• Facilitates the most efficient restores from and to the target site
• Supports Veeam WAN Acceleration
Disadvantages
• Does not leverage Catalyst source-side deduplication for copy job
• V
eeam does achieve its own "source-side when paired with WAN accelerators deduplication", but it’s
limited to a single stream potentially becoming a bottleneck for achieving off-site RPOs
© 2016 Veeam Software
19
Veeam with HPE StoreOnce Catalyst Configuration Guide
Architecture "B" — Site to site using only source gateway servers with Catalyst
Advantages
• Adds an additional layer of intelligence for off-site data transfer by leveraging StoreOnce Catalyst
source-side deduplication, maximizing available WAN bandwidth
Disadvantages
• Does not support Veeam’s health check and heal functionality for backup files
• Does not support Veeam WAN acceleration
• Restore performance from off-site backups may be affected and requires additional configuration
© 2016 Veeam Software
20
Veeam with HPE StoreOnce Catalyst Configuration Guide
Implementation steps for copying Veeam
backups to a remote site
Veeam backup copy jobs are designed to copy backups of single VMs, or entire backup jobs with many
VMs, to a remote location with simple or tiered retention (Grandfather-Father-Son, or GFS). The use of
backup copy jobs plays a key part in complying with 3-2-1 backup best practices — three copies of
data on two different media types, with at least one off-site copy.
Architecture "A" configuration
In this section we are going to show the configuration of the preferred backup copy method where
Veeam has a gateway server at both locations.
1. C
reate a remote Catalyst Store — Create this Catalyst store as you would an on-site store as data
will be written from the gateway server on the local site.
© 2016 Veeam Software
21
Veeam with HPE StoreOnce Catalyst Configuration Guide
2. A
dd a new Windows Server — This will be the remote gateway server, so ensure that it has access
to the remote store created in the previous step.
• Click on “Backup Infrastructure” in Veeam Backup & Replication
• Right click on “Managed Servers” and choose “Add Server”
• Choose Microsoft Windows
© 2016 Veeam Software
22
Veeam with HPE StoreOnce Catalyst Configuration Guide
• Provide the server DNS name or IP address
• Provide local administrator credentials for the new server
© 2016 Veeam Software
23
Veeam with HPE StoreOnce Catalyst Configuration Guide
• Continue through the wizard and finish — Veeam will now install target data mover services to
make this server capable of being a gateway server
3. Create a new backup repository
• F ollow all of the steps of the initial backup repository with exception of choosing the new Windows
Server (located at the remote site) as the gateway server
© 2016 Veeam Software
24
Veeam with HPE StoreOnce Catalyst Configuration Guide
4. Create a Veeam backup copy job
• U
nder “Backup & Replication” click on the “Backup Copy” toolbar button and choose the appropriate
hypervisor for the VMs within your primary backup file
• Give the job a name and choose the interval in which you want backup copies to be made — this
can be done in minutes, hours or per day. At the start of each copy interval, Veeam will look for new
restore points on the primary repository to copy to the target location
• C
hoose the VM backups to be copied off site by choosing either backups, jobs or infrastructure.
When choosing infrastructure or jobs, the copy job will wait until backups for the selected objects
appear on the backup repository before transporting any data
© 2016 Veeam Software
25
Veeam with HPE StoreOnce Catalyst Configuration Guide
Note: You can also selectively choose the backup repository that you would like the backup copy to be
sourced from under “Source.”
• Backup repository — Choose the target StoreOnce Catalyst repository and the retention you
would like to keep for the copied VM backups. You have the option to choose a tiered GFS
retention schedule by checking “Keep the following restore points for archival purposes.” For remote
StoreOnce Catalyst repositories you will leave the “Read the entire restore point from source backup”
option disabled as full backups will be created by virtually synthesizing existing restore points on
the remote StoreOnce appliance
© 2016 Veeam Software
26
Veeam with HPE StoreOnce Catalyst Configuration Guide
• D
ata Transfer — Veeam Backup & Replication can send VM backup data between two StoreOnce
appliances one of two ways:
• D
irect — Data is sent directly between the source and target gateway servers, sending only
unique incremental data after the initial full copy
• T hrough built-in WAN accelerators — Data is sent through Veeam WAN accelerators to minimize
Veeam backup copy traffic on WAN links by using source and target caches of data blocks
already sent between the locations. Typically, this option is recommended on WAN connections
of less than 100 Mbps. A detailed overview of WAN accelerators and instructions for deployment
can be found in the Veeam Backup & Replication User Guide
© 2016 Veeam Software
27
Veeam with HPE StoreOnce Catalyst Configuration Guide
• Schedule — By default, backup copy jobs are set to run continuously between copy intervals, waiting for
new restore points that meet the interval’s requirements. You can, however, set a backup copy window
where the job does not copy data — for example during hours of heavy infrastructure utilization
• Click “Next” and “Finish” the wizard
© 2016 Veeam Software
28
Veeam with HPE StoreOnce Catalyst Configuration Guide
Architecture "B" configuration
In this section we are going to show the configuration of using Veeam backup copy between two
locations with only source Veeam gateways.
1. Create a remote Catalyst Store — In this configuration you are going to choose Low Bandwidth/Low
Bandwidth transfer policies to enable StoreOnce source-side deduplication, compression and checksum.
2. Create a new Backup Repository
• Follow all of the same steps for creating a backup repository, choosing either automatic selection or
explicitly choosing the “Gateway Server” on the primary site
3. Create a backup copy job
All of the same steps will be performed with this architecture when configuring copy jobs with the
exception of two specific settings:
• Veeam Storage Corruption Guard must be unselected under "Advanced" as it is not supported
with this configuration.
© 2016 Veeam Software
29
Veeam with HPE StoreOnce Catalyst Configuration Guide
• Direct data transfer must be used as WAN accelerators are not supported
Architecture “B” restore configuration
All restores from a Catalyst Store must be read back through a gateway server, which is not included
at the off-site location by default in Architecture “B.” It is recommended to add at least one gateway
server at the remote location specifically for restore purposes because of this. Many of the same steps
described earlier in this guide apply for this configuration, but here is a summary:
• Add a Windows Server — This should be located at the offsite location
• Create a new Veeam Backup Repository
• Use the off-site StoreOnce’s IP and credentials
• C
hoose the same off-site Catalyst Store as created in the setup
of Architecture “B” for the repository
• Choose the newly added Windows Server as the gateway server and the mount server
Once added, this repository can be periodically rescanned and newly found backups will appear alongside
disk and disk (copy) backups with a name of disk (imported). Completing restores against these backups
in place of backups found under disk (copy) with Architecture “B” will ensure the most efficient transfer of
data, especially for smaller, more granular restores such as application items and OS files.
© 2016 Veeam Software
30
Veeam with HPE StoreOnce Catalyst Configuration Guide
Utilizing backups
Once primary and backup copy jobs have completed, backups for each job will be found under
Backups>Disk for primary backups, Backups>Disk (copy) for backups created using backup copy
jobs, or Backup>Disk (imported) for backups imported from backup repositories that aren’t tied to a
backup or backup copy job. Restores can be performed simply by right-clicking on the VMs you would
like to restore and using the desired option.
Note: Application item restore options will not appear for VMs containing supported applications if “Guest
Aware Image Processing” isn’t chosen in the backup job.
Resources
• Veeam Backup & Replication User Guide for Hyper-V or VMware
• Veeam Community Forums — Backup and Replication
• HPE Storage Page
• HPE-VEEAM Page on Veeam.com
• HPE Business Support Center Veeam Support
© 2016 Veeam Software
31
Veeam with HPE StoreOnce Catalyst Configuration Guide
About Veeam Software
Veeam® recognizes the new challenges companies across the globe face in enabling the AlwaysOn Business™, a business that must operate 24/7/365. To address this, Veeam has pioneered a
new market of Availability for the Always-On Enterpriser™ by helping organizations meet recovery
time and point objectives (RTPO™) of less than 15 minutes for all applications and data, through
a fundamentally new kind of solution that delivers high-speed recovery, data loss avoidance,
verified protection, leveraged data and complete visibility. Veeam Availability Suite™, which
includes Veeam Backup & Replication™, leverages virtualization, storage, and cloud technologies
that enable the modern data center to help organizations save time, mitigate risks, and
dramatically reduce capital and operational costs.
Founded in 2006, Veeam currently has 37,000 ProPartners and more than 183,000 customers
worldwide. Veeam's global headquarters are located in Baar, Switzerland, and the company has
offices throughout the world. To learn more, visit http://www.veeam.com.
© 2016 Veeam Software
32
Veeam with HPE StoreOnce Catalyst Configuration Guide
NEW Veeam
Availability
™
Suite v9
®
RTPO™ <15 minutes for
ALL applications and data
Learn more and preview
the upcoming v9 release
vee.am/v9
© 2016 Veeam Software
33