Veeam Backup & Replication 6.1 VMware 用户指南：简化虚拟机管理与备份

需积分: 10 168 浏览量更新于2024-07-26 收藏 5.14MB PDF 举报

Veeam Backup & Replication Version 6.1 User Guide for VMware Environments提供了对Veeam备份软件的深入理解，该软件专注于在VMware环境中提供卓越的虚拟机备份解决方案。这款工具因其用户友好的界面（UI）和强大的功能而受到管理员的青睐，它允许管理员对数据中心内的虚拟机进行集中管理和高效备份，从而确保数据安全和灾难恢复能力。在本用户指南中，重点介绍的是针对VMware环境定制的特性，包括但不限于以下几点： 1. **统一管理**：Veeam Backup & Replication提供了一套全面的平台来管理整个备份流程，管理员可以轻松配置和监控多个虚拟机的备份策略，简化了日常运维工作。 2. **备份功能**：版本6.1可能包含了增量备份、差异备份和全量备份等多种方式，以适应不同的业务需求。通过这些方法，可以减少备份时间、存储空间占用，并提高恢复速度。 3. **高效性与性能**：利用VMware特定优化，Veeam可能采用了快照技术或者低I/O模式来减少对虚拟机运行的影响，确保备份过程对业务的干扰最小化。 4. **兼容性和集成**：文档强调了与VMware vSphere的紧密集成，包括对vSphere API的支持，这使得与其他VMware工具和服务（如vMotion、DRS等）无缝协同工作。 5. **安全与合规**：Veeam Backup & Replication可能包含加密选项，确保数据在传输和存储过程中得到保护，符合各种数据保护法规要求。 6. **易用性与文档支持**：作为用户指南的一部分，它详细解释了如何设置、配置和操作备份任务，以及如何处理常见的问题和故障排查，便于新手快速上手。 7. **更新与技术支持**：指出信息可能会随时间而更新，用户应查阅最新文档以获取最准确的技术支持，因为Veeam Software Inc.保留随时更改的权利。 8. **法律责任声明**：尽管Veeam Backup & Replication提供了丰富的功能，但公司并不对文档中的技术或编辑错误负责，且可能存在专利权、商标权等知识产权，用户使用时需遵循相应的许可协议。 Veeam Backup & Replication Version 6.1 User Guide for VMware Environments是一份实用的资源，旨在帮助管理员充分利用该软件的强大功能，提升数据中心的数据保护能力和恢复响应速度。在实际操作中，遵循文档指导并根据具体环境调整策略至关重要。

16 | Veeam Backup & Replication | VMware Environments | USER GUIDE | REV 1

Advanced Deployment

In large-scale virtual environments with a great number of jobs, the load on the Veeam Backup

Server is heavy. In this case, it is recommended to use the advanced deployment scenario which

moves the backup workload to dedicated backup proxies and backup repositories.

The essence of the advanced deployment is that the backup proxy takes off a part of Veeam

Backup server activities – namely, it collects and processes data and moves backup traffic from

source to target. In addition, the Veeam Backup server no longer acts as a storage location – the

backup proxy transports VM data to the backup repository which is the location for keeping

backup files, VM copies, metadata and so on. The Veeam Backup server in this scenario functions as

a ‘manager’ for backup proxies and repositories.

To configure a backup proxy and a backup repository, you should add servers to

Veeam Backup & Replication and assign proxy and repository roles to them.

Veeam Backup & Replication will automatically install light-weight components and services onto

these servers. Backup proxies do not require SQL – all settings are stored centrally, within the SQL

database used by the Veeam Backup server.

With the advanced deployment scenario, you can easily meet your current and future data

protection requirements. You can expand your backup infrastructure horizontally in a matter of

minutes to match the amount of data you want to process and available network throughput.

Instead of growing the number of backup servers or constantly tuning job scheduling, you can

install multiple backup proxies and repositories and distribute the backup workload among them.

The installation process is fully automated, which simplifies deployment and maintenance of the

backup infrastructure in your virtual environment.

In virtual environments with several proxies, Veeam Backup & Replication dynamically distributes

the backup traffic among these proxies. A job can be explicitly mapped to a specific proxy.

Alternatively, you can let Veeam Backup & Replication choose a proxy. In this case,

Veeam Backup & Replication will check settings of available proxies and select the most

appropriate one for the job. The proxy server to be used should have access to the source and

target as well as a backup repository to which files will be written.

The advanced deployment scenario can be a good choice for backing up and replicating off-site.

You can deploy a backup proxy in the production site and another one closer to the backup

repository. When a job is performed, backup proxies on both sides establish a stable connection,

so this architecture also allows for efficient transport of data over a slow network connection or

WAN.

To regulate backup load, you can specify the maximum number of concurrent tasks per proxy and

set up throttling rules to limit proxy bandwidth. The maximum number of concurrent tasks can

also be specified for a backup repository; additionally, you can define combined ingestion rate for

it.

17 | Veeam Backup & Replication | VMware Environments | USER GUIDE | REV 1

Another advantage of the advanced deployment scenario is that it contributes to high availability

– jobs can migrate between proxies if one of them becomes overloaded or unavailable.

Distributed Deployment

The distributed deployment scenario is recommended for large geographically dispersed virtual

environments with multiple Veeam Backup servers installed across different sites. These backup

servers are federated under Veeam Backup Enterprise Manager – an optional component that

provides centralized management and reporting for these servers through a web interface.

Veeam Backup Enterprise Manager collects data from Veeam Backup servers and enables you to

run backup and replication jobs across the entire backup infrastructure through a single pane of

glass, edit them and clone jobs using a single job as a template. It also provides reporting data for

various areas – for example, all jobs performed within the last 24 hours or 7 days, all VMs engaged

in these jobs and so on. Using indexing data consolidated on one server, Veeam Backup Enterprise

Manager provides advanced capabilities to search for guest OS files of Windows-based VMs

through backups created on all Veeam Backup servers (even if they are stored in repositories on

different sites), and recover them in one click. Search for guest OS files is enabled through Veeam

Backup Enterprise Manager itself; to streamline the search process, you can optionally deploy a

Veeam Backup Search server in your backup infrastructure.

If you use Veeam Backup Enterprise Manager in your backup infrastructure, you do not need to

install licenses on every Veeam Backup server you deploy. Instead, you can install one license on

the Veeam Backup Enterprise Manager server, and it will be applied to all servers across your

backup infrastructure. This approach simplifies tracking license usage and license updates across

multiple Veeam Backup Servers.

Resource Scheduling

With its inbuilt mechanism of resource scheduling, Veeam Backup & Replication is capable to

automatically select and use optimal resources to run configured jobs. Resource scheduling is

performed by the Veeam Backup Service running on the Veeam Backup server. When a job starts, it

communicates with the service to inform it about the resources it needs. The service analyzes job

settings, parameters specified for backup infrastructure components, current load on the

components, and automatically allocates optimal resources to the job.

For resource scheduling, the Veeam Backup service considers the following settings in the backup

infrastructure:

• Network traffic throttling

• Maximum number of concurrent tasks for backup proxies and backup repositories

• Data ingestion rate for backup repositories

18 | Veeam Backup & Replication | VMware Environments | USER GUIDE | REV 1

Network Traffic Throttling and Multithreaded Data Transfer

To limit the impact of Veeam Backup & Replication jobs on the network performance, you can

throttle network traffic for Veeam Backup & Replication jobs. Network traffic throttling prevents

jobs from utilizing the entire bandwidth available in your environment and makes sure that

enough traffic is provided for other critical network operations. It is especially recommended that

you throttle network traffic if you perform off-site backup or replicate VMs to a DR site over slow

WAN links.

In Veeam Backup & Replication, network traffic throttling is implemented through rules that apply

to backup proxies, so you do not have to make any changes to your network infrastructure.

Network traffic throttling rules are enforced globally, at the level of the Veeam Backup server. Every

throttling rule limits the maximum throughput of traffic going between two backup proxies (in

case of replication), between a backup proxy and a repository (in case of backup), or between a

backup proxy and a proxying Windows server (in case of backup to an SMB share).

Rules are set for a pair of IP address ranges (the range can include a single IP address), and are

applied to the source backup proxy and the target server (backup proxy, repository or proxying

server) between which data is transferred over the network.

When a new job starts, Veeam Backup & Replication checks network traffic throttling rules against

a pair of backup proxies assigned for the job – a backup proxy on the source side and a server

(backup proxy, backup repository or proxying server) on the target side. If the source and target IP

addresses fall into specified IP ranges, the rule will be applied. For example, if for a network traffic

throttling rule you specify 192.168.0.1 - 192.168.0.255 as the source range and 172.16.0.1 –

172.16.0.255 as the target range, and the backup proxy on the source side has IP address

192.168.0.12, while the target backup proxy has IP address 172.16.0.31, the rule will be applied. The

network traffic going from this backup proxy to the target side will be throttled.

Note Please keep in mind that throttling rules are reversible (that is, they function in two directions). If

the IP address of the proxy on the source side falls into the target IP range, and the IP address of

the proxy on the target side falls into the source IP range, the rule will be applied in any case.

The Veeam Backup server equally splits available bandwidth between all jobs that use backup

proxies to which a network throttling rule applies. For example, if you run one job that uses a pair

of proxies to which the rule applies, the job will get the entire bandwidth allowed by the rule. If

you run two jobs at a time, the allowed bandwidth will be equally split between them. As soon as

one of the jobs completes, the bandwidth assigned to it will be freed, and the remaining job will

use the entire bandwidth allowed by the rule.

19 | Veeam Backup & Replication | VMware Environments | USER GUIDE | REV 1

Throttling rules can be scheduled for specific time intervals – for example, during business hours.

This way, you will minimize the impact of job performance spikes on the production network.

Alternatively, you can select to apply throttling rules regardless of the time.

In addition to traffic throttling, Veeam Backup & Replication offers another possibility for network

traffic management – management of data transfer connections. Normally, within one backup

session Veeam Backup & Replication opens 5 parallel TCP/IP connections to transfer data from

source to target. Multithreaded data transfer increases the transfer speed but can place additional

load on the network. If required, you can disable multithreaded data transfer and limit the number

of connections per session to 1.

Limiting the Number of Concurrent Tasks

To avoid overload of backup proxies and backup repositories, Veeam Backup & Replication allows

you to limit the number of concurrent tasks performed on a backup proxy, or tasks targeted at a

backup repository.

When a new job starts, Veeam Backup & Replication analyzes the list of VMs that the job includes,

and creates a separate task for every VM. Tasks of the same jobs are accomplished in turn, that is,

VMs in the same job are processed one by one. Before processing a new task,

Veeam Backup & Replication detects what backup infrastructure components (backup proxies and

repositories) will be involved.

Task limiting is performed by the Veeam Backup Service that is aware of all backup proxies and

backup repositories connected to it, and settings specified for these backup proxies and

repositories, namely the number of allowed concurrent tasks. Every job running in the backup

infrastructure informs the Veeam Backup Service about its tasks at a 10 second interval. Before a

new task targeted at a specific backup proxy or repository starts, the Veeam Backup Service checks

the current workload (the number of tasks currently working with the proxy or repository) and the

number of allowed tasks per this component. If this number is exceeded, a new task will not start

until one of the currently running jobs is finished.

Limiting Data Ingestion Rate for Backup Repositories

With Veeam Backup & Replication, you can limit the data ingestion rate for backup repositories.

The Veeam Backup Service is aware of data ingestion settings configured for all repositories in the

backup infrastructure. When a job targeted at some backup repository is performed, the Veeam

Backup Service informs the Veeam agent running on the repository about the allowed write speed

specified for this repository so that the agent can limit the write speed to the specified value.

If the repository is used by a number of jobs, the allowed write speed is equally split between all of

them.

Detecting Performance Bottlenecks

As any backup application handles a great amount of data, it is important to make sure the data

flow is efficient and all resources engaged in the backup process are optimally used. During a job

run, VM data blocks are processed in cycles. Every cycle includes a number of stages – reading data

blocks from source, processing data on the backup proxy, transmitting data over the network and

20 | Veeam Backup & Replication | VMware Environments | USER GUIDE | REV 1

writing data to target. VM data therefore is passed over the data pipe. When one data processing

cycle is over, the next cycle begins.

Veeam Backup & Replication provides advanced statistics about the data path performance and

lets you identify bottlenecks in the data transmission process.

To evaluate the data flow efficiency, Veeam Backup & Replication analyzes performance of all

components in the data pipe working as the cohesive system, and evaluates key factors on the

source and target sides.

(1) Source – the source disk reader component responsible for retrieving data from the

source storage.

(2) Proxy – the backup proxy component responsible for processing VM data.

(3) Network – the network queue writer component responsible for getting processed VM

data from the backup proxy and sending it over the network to the backup repository or

another backup proxy.

(4) Target – the target disk writer component (backup storage or replica datastore).

The resource usage level for the four points is evaluated in percent. This percent rate defines the

amount of time for which components are busy during the job. When you run a job, the VM data is

sent continuously over the data pipe to the destination, block by block. An efficient data flow

assumes that there is no latency at any point of the data pipe and all its components work for

approximately equal amount of time. If any of the components operates inefficiently, there may

appear a bottleneck in the data path. The insufficient component will work 100% of time while the

others will be idling, waiting for data to be transferred. As a result, the whole data flow will slow

down to the level of the slowest point in the data path, and the overall time of data processing will

increase.

To identify a bottleneck in the data path, Veeam Backup & Replication detects the component with

the maximum workload – that is, the component that works for the most time of the job. For

example, you use a low-speed storage device as the backup repository. Even if VM data is retrieved

from SAN storage on the source side and transmitted over a high-speed link, VM data flow will still

be impaired at the backup repository. The backup repository will be trying to consume transferred

data at the rate that exceeds its capacity, and the other components will stay idle. As a result, the

backup repository will be working 100% of job time, while other components may be employed,

for example, for 60% only. In terms of Veeam Backup & Replication, such data path will be

considered insufficient.

The bottleneck statistics for a job is displayed in the job session data. The bottleneck statistics does

not necessarily mean that you have a problem in your backup infrastructure – it simply informs you

about the weakest component in the data path. However, if you feel the job performance is low,

you may try taking some measures to resolve the bottleneck. For instance, in the case described

above, you can limit the number of concurrent tasks for the backup repository.

Backup

Unlike traditional backup tools designed to work with physical machines,

Veeam Backup & Replication is built specifically for virtual environments. It operates at the

virtualization layer and uses an image-based approach for virtual machines backup. To retrieve

VM data, no agent software needs to be installed inside the guest OS – instead,

Veeam Backup & Replication leverages ESX snapshot capabilities. When a new backup session

剩余229页未读，继续阅读

antagonism1985

粉丝: 0
资源: 2

Veeam Backup & Replication 6.1 VMware 用户指南：简化虚拟机管理与备份

Python库 veeam_easy_connect-0.3.0 功能解析与安装指南

Python库 veeam_easy_connect-0.4.0.tar.gz 安装与使用

Veeam Backup & Replication 9.5 VMware vSphere用户指南

veeam_backup_9_5_user_guide_vsphere_en

veeam_backup_11_0_user_guide_vsphere.pdf

veeam_backup_9_5_u4_user_guide_vsphere_pg_IT软件公司技术售前方案.pdf

veeam_backup_9_x_uair_wizard_user_guide_pg_IT软件公司技术售前方案.pdf

veeam_backup_9_5_u4_explorers_user_guide_pg_IT软件公司技术售前方案.pdf

veeam_backup_9_5_u4_tapes_user_guide_pg_IT软件公司技术售前方案.pdf

veeam_backup_9_5_u4_user_guide_hyperv_pg_IT软件公司技术售前方案.pdf

最新资源