Deployment Scenario

A deployment scenario (DS) topic describes a specific deployment scenario.

When to Use DS Topic

Every solution supports a number of deployment scenarios. Use this topic type in case you want to explain one of these scenarios.

How to Use DS Topic

This topic structure consists of the following elements:

  1. Title — the name of a deployment scenario.

Use a descriptive title that briefly summarizes the solution architecture in this deployment scenario.

  1. Rationale — reasons for the deployment scenario.

Explain why users could choose this scenario to deploy the solution.

  1. Conditions — limitations that exist in the deployment scenario.

Specify conditions applied to the solution deployment in this scenario.

Do not dive too deep into details. For example, do not list prerequisites and system requirements — this is what the System Requirements section is for.

  1. Components — a list of deployed solution components.

Describe the solution architecture and its components in the deployment scenario:

  1. [Optional] Advantages and disadvantages — the pros and cons of using the deployment scenario.

If there are not enough advantages and disadvantages to create a separate section, add this information to the Objectives section.

  1. Diagram — an illustration of the deployment scenario.

Add a diagram to illustrate the description of components. Make sure you show in the diagram only those components that you include in the description.

 

Deployment Topic

Deployment ScenarioExample

Advanced Deployment [title]

In large-scale virtual environments with a large number of jobs, the load on the backup server is heavy. In this case, it is recommended that you use the advanced deployment scenario that moves backup workloads to dedicated backup infrastructure components. Here, the backup server functions as a "manager" for deploying and maintaining backup infrastructure components. [rationale]

With the advanced deployment scenario, you can easily meet your current and future data protection requirements. You can horizontally expand your backup infrastructure in a matter of minutes to match the amount of data you want to process and the available network throughput. Instead of growing the number of backup servers or constantly tuning job scheduling, you can install multiple backup infrastructure components and distribute the backup workload among them. The installation process is fully automated, which simplifies the deployment and maintenance of the backup infrastructure in your virtual environment. [advantages]

The advanced deployment includes the following components: [components]

  • Virtual infrastructure servers — VMware vSphere hosts used as the source and target for backup, replication and VM copy.
  • Backup server — the configuration and management center of the backup infrastructure.
  • Backup proxy — a "data mover" component used to retrieve VM data from the source datastore, to process it and to deliver to the target.
  • Backup repository — a location used to store backup files, VM copies and auxiliary replica files.
  • Dedicated mount servers — a component required to restore VM guest OS files and application items to the original location.
  • Dedicated guest interaction proxy — a component used to deploy the runtime process in Microsoft Windows VMs.

Deployment Scenario 

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.