Free Windows Backup Solution for PCs and Endpoints Skip to content
 

Veeam Backup & Replication Offline Installer

Veeam Backup & Replication Offline Installer

Veeam Backup & Replication Offline Installer

Veeam Backup & Replication 10 Free Download New and latest Version for Windows. It is full offline installer standalone setup of Veeam. Backup and Recovery for all workloads – VMware, Hyper-V, Windows, AWS and more! integration into Veeam Backup & Replication™ and more. On the other hand, if the Veeam Agent for Microsoft Windows installation package is installed.

Veeam Backup & Replication Offline Installer -

Backup to Azure with Veeam

This article helps you integrate a Veeam infrastructure with Azure Blob storage. It includes prerequisites, considerations, implementation, and operational guidance. This article addresses using Azure as an offsite backup target and a recovery site if a disaster occurs, which prevents normal operation within your primary site.

Note

Veeam also offers a lower recovery time objective (RTO) solution, Veeam Backup & Replication with support for Azure VMware Solution workloads. This solution lets you have a standby VM that can help you recover more quickly in the event of a disaster in an Azure production environment. Veeam also offers Direct Restore to Microsoft Azure and other dedicated tools to back up Azure and Office 365 resources. These capabilities are outside the scope of this document.

Reference architecture

The following diagram provides a reference architecture for on-premises to Azure and in-Azure deployments.

Veeam to Azure reference architecture diagram.

Your existing Veeam deployment can easily integrate with Azure by adding an Azure storage account, or multiple accounts, as a cloud backup repository. Veeam also allows you to recover backups from on-premises within Azure giving you a recovery-on-demand site in Azure.

Veeam interoperability matrix

WorkloadGPv2 and Blob StorageCool tier supportArchive tier supportData Box Family support
On-premises VMs/datav10av10aN/A10a*
Azure VMsv10av10aN/A10a*
Azure Blobv10av10aN/A10a*
Azure Filesv10av10aN/A10a*

Veeam has offered support for above Azure features in older versions of their product as well, for optimal experience leveraging the latest product version is strongly recommended.

*Veeam Backup and Replication support REST API only for Azure Data Box. Therefore, Azure Data Box Disk is not supported. Please see details for Data Box support here.

Before you begin

A little upfront planning will help you use Azure as an offsite backup target and recovery site.

Get started with Azure

Microsoft offers a framework to follow to get you started with Azure. The Cloud Adoption Framework (CAF) is a detailed approach to enterprise digital transformation and comprehensive guide to planning a production grade cloud adoption. The CAF includes a step-by-step Azure Setup Guide to help you get up and running quickly and securely. You can find an interactive version in the Azure portal. You'll find sample architectures, specific best practices for deploying applications, and free training resources to put you on the path to Azure expertise.

Consider the network between your location and Azure

Whether using cloud resources to run production, test and development, or as a backup target and recovery site, it's important to understand your bandwidth needs for initial backup seeding and for ongoing day-to-day transfers.

Azure Data Box provides a way to transfer your initial backup baseline to Azure without requiring more bandwidth. This is useful if the baseline transfer is estimated to take longer than you can tolerate. You can use the Data Transfer estimator when you create a storage account to estimate the time required to transfer your initial backup.

Shows the Azure Storage data transfer estimator in the portal.

Remember, you'll require enough network capacity to support daily data transfers within the required transfer window (backup window) without impacting production applications. This section outlines the tools and techniques that are available to assess your network needs.

Determine how much bandwidth you'll need

Multiple assessment options are available to determine change rate and total backup set size for the initial baseline transfer to Azure. Here are some examples of assessment and reporting tools:

Determine unutilized internet bandwidth

It's important to know how much typically unutilized bandwidth (or headroom) you have available on a day-to-day basis. This helps you assess whether you can meet your goals for:

  • initial time to upload when you're not using Azure Data Box for offline seeding
  • completing daily backups based on the change rate identified earlier and your backup window

Use the following methods to identify the bandwidth headroom that your backups to Azure are free to consume.

Choose the right storage options

When you use Azure as a backup target, you'll make use of Azure Blob storage. Blob storage is Microsoft's object storage solution. Blob storage is optimized for storing massive amounts of unstructured data, which is data that does not adhere to any data model or definition. Additionally, Azure Storage is durable, highly available, secure, and scalable. You can select the right storage for your workload to provide the level of resiliency to meet your internal SLAs. Blob storage is a pay-per-use service. You're charged monthly for the amount of data stored, accessing that data, and in the case of cool and archive tiers, a minimum required retention period. The resiliency and tiering options applicable to backup data are summarized in the following tables.

Blob storage resiliency options:

Locally-redundantZone-redundantGeo-redundantGeo-zone-redundant
Effective # of copies3366
# of availability zones1324
# of regions1122
Manual failover to secondary regionN/AN/AYesYes

Blob storage tiers:

Hot tierCool tierArchive tier
Availability99.9%99%Offline
Usage chargesHigher storage costs, Lower access, and transaction costsLower storage costs, higher access, and transaction costsLowest storage costs, highest access, and transaction costs
Minimum data retention requiredNA30 days180 days
Latency (time to first byte)MillisecondsMillisecondsHours

Sample backup to Azure cost model

With pay-per-use can be daunting to customers who are new to the cloud. While you pay for only the capacity used, you do also pay for transactions (read and or writes) and egress for data read back to your on-premises environment when Azure Express Route direct local or Express Route unlimited data plan are in use where data egress from Azure is included. You can use the Azure Pricing Calculator to perform "what if" analysis. You can base the analysis on list pricing or on Azure Storage Reserved Capacity pricing, which can deliver up to 38% savings. Here's an example pricing exercise to model the monthly cost of backing up to Azure. This is only an example. Your pricing may vary due to activities not captured here.

Cost factorMonthly cost
100 TB of backup data on cool storage$1556.48
2 TB of new data written per day x 30 days$42 in transactions
Monthly estimated total$1598.48
------------------
One time restore of 5 TB to on-premises over public internet$527.26

Note

This estimate was generated in the Azure Pricing Calculator using East US Pay-as-you-go pricing and is based on the Veeam default of 512 kb chunk size for WAN transfers. This example may not be applicable towards your requirements.

Implementation guidance

This section provides a brief guide for how to add Azure Storage to an on-premises Veeam deployment. For detailed guidance and planning considerations, we recommend you take a look at the following Veeam Guidance for their Capacity Tier.

  1. Open the Azure portal, and search for Storage Accounts. You can also click on the default service icon.

    Shows adding a storage accounts in the Azure portal.

    Shows where you've typed storage in the search box of the Azure portal.

  2. Select Create to add an account. Select or create a resource group, provide a unique name, choose the region, select Standard performance, always leave account kind as Storage V2, choose the replication level which meets your SLAs, and the default tier your backup software will apply. An Azure Storage account makes hot, cool, and archive tiers available within a single account and Veeam policies allow you to use multiple tiers to effectively manage the lifecycle of your data.

    Shows storage account settings in the portal

  3. Keep the default networking and data protection options for now. Do not enable Soft Delete for Storage Accounts storing Veeam capacity tiers.

  4. Next, we recommend the default settings from the Advanced screen for backup to Azure use cases.

    Shows Advanced settings tab in the portal.

  5. Add tags for organization if you use tagging, and create your account.

  6. Two quick steps are all that are now required before you can add the account to your Veeam environment. Navigate to the account you created in the Azure portal and select Containers under the Blob service menu. Add a container and choose a meaningful name. Then, navigate to the Access keys item under Settings and copy the Storage account name and one of the two access keys. You will need the container name, account name, and access key in the next steps.

    Shows container creation in the portal.

    Shows access key settings in the portal.

    Note

    Veeam Backup and Replication offers additional options to connect to Azure. For the use case of this article, using Microsoft Azure Blob Storage as a backup target, using the above method is the recommended best practice.

  7. (Optional) You can add more layers of security to your deployment.

    1. Configure role-based access to limit who can make changes to your storage account. For more information, see Built-in roles for management operations.

    2. Restrict access to the account to specific network segments with storage firewall settings to prevent access attempts from outside your corporate network.

      Shows storage firewall settings in the portal.

    3. Set a delete lock on the account to prevent accidental deletion of the storage account.

      Resource Lock

    4. Configure additional security best practices.

  8. In the Veaam Backup and Replication Management Console, navigate to Backup Infrastructure -> right-click in the overview pane and select Add Backup Repository to open the configuration wizard. In the dialog box, select Object storage -> Microsoft Azure Blob Storage -> Azure Blob Storage.

    Shows selecting object storage in the Veeam Repository Wizard.

    Shows selecting Microsoft Azure Blob Storage in the Veeam Repository Wizard.

    Shows selecting Azure Blob Storage in the Veeam Repository Wizard.

  9. Next, specify a name and a description of your new Blob storage repository.

    Shows typing a name for the repository in the Veeam Repository Wizard.

  10. In the next step, add the credentials to access your Azure storage account. Select Microsoft Azure Storage Account in the Cloud Credential Manager, and enter your storage account name and access key. Select Azure Global in the region selector, and any gateway server if applicable.

    Shows specifying an account in the Veeam Repository Wizard.

    Note

    If you choose not to use a Veeam gateway server, make sure that all scale-out repository extents have direct internet access.

  11. On the container register, select your Azure Storage container and select or create a folder to store your backups in. You can also define a soft limit on the overall storage capacity to be used by Veeam, which is recommended. Review the displayed information in the summary section and complete the configuration tool. You can now select the new repository in your backup job configuration.

    Shows specifying a container in the Veeam Repository Wizard.

    Shows creating a folder in the Veeam Repository Wizard.

Operational guidance

Azure alerts and performance monitoring

It is advisable to monitor both your Azure resources and Veeam's ability to leverage them as you would with any storage target you rely on to store your backups. A combination of Azure Monitor and Veeam's monitoring capabilities (the Statistics tab in the Jobs node of the Veeam Management Console or more advanced options like Veeam One Reporter) will help you keep your environment healthy.

Azure portal

Azure provides a robust monitoring solution in the form of Azure Monitor. You can configure Azure Monitor to track Azure Storage capacity, transactions, availability, authentication, and more. The full reference of metrics tracked may be found here. A few useful metrics to track are BlobCapacity - to make sure you remain below the maximum storage account capacity limit, Ingress and Egress - to track the amount of data being written to and read from your Azure storage account, and SuccessE2ELatency - to track the roundtrip time for requests to and from Azure Storage and your MediaAgent.

You can also create log alerts to track Azure Storage service health and view the Azure status dashboard at any time.

Veeam reporting

How to open support cases

When you need help with your backup to Azure solution, you should open a case with both Veeam and Azure. This helps our support organizations to collaborate, if necessary.

To open a case with Veeam

On the Veeam customer support site, sign in, and open a case.

To understand the support options available to you by Veeam, see the Veeam Customer Support Policy.

You may also call to open a case: Worldwide support numbers

To open a case with Azure

In the Azure portal search for support in the search bar at the top. Select Help + support -> New Support Request.

Note

When you open a case, be specific that you need assistance with Azure Storage or Azure Networking. Do not specify Azure Backup. Azure Backup is the name of an Azure service and your case will be routed incorrectly.

Links to relevant Veeam documentation

See the following Veeam documentation for further detail:

Marketplace offerings

You can continue to use the Veeam solution you know and trust to protect your workloads running on Azure. Veeam has made it easy to deploy their solution in Azure and protect Azure Virtual Machines and many other Azure services.

Next steps

See the following resources on the Veeam website for information about specialized usage scenarios:

Источник: https://docs.microsoft.com/en-us/azure/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/veeam/veeam-solution-guide

Introduction

This guide will help you log into the Veeam Availability Console and install the necessary tools you need to start a backup job. We will also show you how to configure both tools to meet your requirements.

Perform the steps below on the computer that you want to back up, unless stated otherwise.

How to install Veeam Availability Console Agents

Prerequisites

  • Veeam Availability Console credentials phoenixNAP provided

STEP 1 – Log in to the PhoenixNAP Veeam Availability Console (VAC)

1. Navigate to https://phxvac.phoenixnap.com/
2. Enter your username in this form: CompanyUser. (For example: MyCompanyChrisP)
3. Enter the password. Optionally, select the “Remember me” checkbox.
4. Click Login.

VAC login page with credentials.

The next screen takes you to the summary page of the console.

STEP 2 – Install Veeam Management Agent

Veeam Management Agent lets you remotely manage and monitor your Veeam Backup and Replication servers.

To install the agent:

1. In VAC, select Managed Computers and click Download Agent.

Download Veeam Management Agent

2. Save the file to the desired location on the computer. Depending on the settings, the file may be automatically saved in the Downloads folder.

3. Open the file, the name should be ManagementAgent. The installation wizard starts.

Note: The server you are backing up needs Microsoft .NET Framework 4.6 or higher. The installer will prompt if any services or an OS reboot is needed. Please confirm if you get such a pop-up.

4. Click Next on the first screen.

Veeam Management Agent wizard step one.

5. Select both boxes “I accept the terms…” if you accept the license agreement and click Next.

Veeam Management Agent wizard license agreement

6. Click Install and wait for the installation to finish.

Veeam Management Agent wizard start the installation.

7. Click Finish when the Wizard completes the installation.

Finish Veeam Management Agent installation.

The agent should start in the background.

STEP 3 – Configure Management Agent Connection

To establish a connection between the Management Agent and the VAC, follow these steps:

1. Find the Management Agent icon on the right side of the taskbar, next to the clock.

2. Click the arrow if the icons are hidden. Then, right-click the Agent icon and select Agent Settings.

Veeam Management Agent icon

3. In the connection configuration window, use the following settings:

Cloud gateway: use one of the FQDNs as a gateway, depending on the server location:

               For Phoenix: phxcloudconnect.phoenixnap.com or phxcloudconnect2.phoenixnap.com

               For Ashburn: ashcloudconnect.phoenixnap.com

               For the Netherlands: nldcloudconnect.phoenixnap.com

               For Atlanta: atlcloudconnect.phoenixnap.com

               For Singapore: sincloudconnect.phoenixnap.com

Port: Enter the default port 6180. It is grayed out, so you need to type it in.

Username: Enter your username without the company part. Refer to the screenshot below.

Password: Enter your password.

Connection configuration window

4. Click Apply.

5. The connection should be established. If you get a certificate error ID 625, then an IP address was used. Use FQDN to resolve the issue. Click Save on the Security Certificate Preview window.

Security Certificate Preview Window

6. Click Restart to apply the settings and wait until Veeam Management Agent restarts.

Restart Veeam Agent Dialog

7. Click Close to exit the settings window when the process completes. The agent status will be green and read Connected.

Agent status window showing connected.

The Management Agent icon in the system tray should no longer have an exclamation mark or a red X.

When you reload the Managed Computers page in VAC, the machine appears on the list.

VAC managed computers list.

STEP 4 – Install Veeam Backup Agent

Veeam Backup Agent allows you to perform an easy and secure backup of a machine to another location.

To install Veeam Backup Agent using the console:

1. Navigate to the Managed Computers screen.

2. Select a machine and click Install Backup Agent.

Install Backup Agent on a selected machine using VAC

3. Specify the credentials to use for the guest OS. You can leave the selection to “Account specified…”

VAC agent specify credentials.

You can also select to specify a user account from the drop-down list or Create New.

Create new user account for backup agent

Specify the credentials in the form Companyuser and click Apply.

4. Choose a Backup Policy from the list. The default selection backs up your server daily.

VAC choosing backup policy

Optionally, you can create a new back up policy and go through detailed configuration.

5. Click Apply after you select a backup policy.

The deployment of Veeam Backup Agent will start on the machine you selected. You can view the progress in the Managed Computers screen. The process is complete when Agent Deployment says Success, and the progress bar reaches 100%.

Backup agent installation progress bar

If you search for the agent on this machine, it will show up in the results:

Windows Start menu with agent icon.

STEP 5 – Configure Veeam Backup Agent and Start a Backup Job

To configure Veeam Backup Agent, you can log into the VACfrom any computer. This step does not require you to log in from the computer you want to backup as was the case in previous steps.

To manually start a backup job:

1. Select Backup Jobs on the left side of the console.

2. Tick the box next to the desired machine. So far, we have one.

3. Click 0 of 1 (the numbers may change) under the Successful Jobs heading.

VAC backup job start

The Agent Jobs page loads.

4. Select a job and click Edit… if you want to change the job configuration.

change the job configuration

5. To save disk space, reduce the number of restore points to less than 14 in the Backup Resources -> Retention Policy section.

VAC job retention policy settings

6. For a server running a database, you can Truncate logs. Navigate to Guest Processing -> Customize application handling options for individual applications and select Truncate logs under the SQL tab.

Enable SQL truncate logs

7. To change when a backup job starts automatically, navigate to Schedule. Set the time and options for automatic retries.

Backup job time and options for automatic retries.

8. Click Finish when ready.

9. Finally, click Start to begin the backup job for the selected machine.

Steps to start backup job in VAC

The console will show a progress bar, but you can also track the progress and status on the machine you are backing up. Open Veeam Agent Control Panel from the system tray or start menu to see the details:

Veeam agent control panel progress in Windows

All current and future backups will appear in the Veeam Agent Control Panel.

Veeam agent all backup jobs

Conclusion

The steps in this article helped you install and configure Veaam Management Agent and Veeam Backup Agent using Veeam Availability Console.

For more details on how to use the VAC, refer to our Quick Start Guide.

Was this article helpful?

YesNo

Источник: https://phoenixnap.com/kb/install-and-configure-veeam-management-agent-and-veeam-backup-agent

Using Veeam with AWS Storage services to store offsite backups

Many customers are using Veeam Backup & Replication to protect their on-premises infrastructure and want to reduce the amount of physical backup infrastructure that they need to purchase and maintain. They also want to ensure that their backups reside in highly durable, cost effective storage. AWS Storage services such as Amazon S3, AWS Storage Gateway, and AWS Snowball Edge seamlessly integrate with Veeam Backup & Replication to meet these needs.

Veeam Backup & Replication enables customers to automatically tier backups to Amazon S3 to help reduce their reliance and costs associated with more expensive on-premises backup storage. Initially released in January 2019 in version 9.5 Update 4, Veeam Backup & Replication has been used by customers such as Best Friends Animal Society (case study) to enhance their DR strategy while providing cost savings. In February 2020, Veeam released Veeam Backup & Replication Version 10, adding additional functionality to capacity tier. Capacity tier is an additional tier of storage that can be attached to a scale-out backup repository.

In this blog post, we review the options and best practices available to Veeam customers looking to integrate with AWS Storage services based on knowledge learned both in the lab and in the field. In addition, we discuss strategies to help you leverage Veeam Backup & Replication to recover your on-premises workloads in AWS as Amazon EC2 instances for disaster recovery (DR) purposes. By the end of this post, you should have a better understanding of how the integration between Veeam Backup & Replication with AWS Storage services works. You will also have information to decide on which approach would work best for your organizations use case, including any caveats to watch out for when implementing these integrations.

Veeam concepts

Let’s look into some of the concepts involved with Veeam Backup & Replication.

Scale-out backup repository (SOBR): A SOBR is a logical entity that consists of one or more backup repositories that are configured as tiers. A SOBR is used as a single target for backup and copy jobs. Customers must configure a SOBR that contains a performance tier that provides fast access to data with locally hosted backup repositories as direct-attach block storage, NAS storage, or a deduplication appliance. The SOBR also enables customers to define a capacity tier that is useful for long-term storage, where Amazon S3 is used as the object storage repository.

Veeam customers can also leverage AWS Snowball Edge as an object storage repository to seed large initial backups to Amazon S3. Snowball Edge is a small, rugged, and secure portable storage and edge computing device used for data collection, processing, and migration. Snowball Edge devices are purpose-built for moving multiple terabytes of data offline to AWS to overcome the challenge of limited bandwidth.Snowball Edge encrypts all data at rest with 256-bit encryption with keys provided by the customer using the AWS Key Management Service (AWS KMS). This can be helpful for customers with large volumes of on-premises backups who may not have the WAN bandwidth to complete the data seeding within an acceptable amount of time. Veeam customers who want to use Snowball Edge must be running Veeam Backup & Replication 10a, which was released in July 2020. For more information on how to set up Snowball Edge as an object storage repository, please review the relevant Veeam documentation.

Scale-out backup repository (SOBR)

Copy and move operations: Customers can choose to configure their capacity tier to have Veeam backups sent to Amazon S3 in two ways. Customers can immediately copy backups to Amazon S3 after the backup job has completed. Alternatively, they can move backups from the performance tier to Amazon S3 once the backup chain has been sealed and it is outside of a defined operational restore window.

Copy operation to capacity tierMove operation to capacity tier
Applies toAny backup (full, incremental, etc.)Sealed backup chains
Offload timeUpon completion of backup jobOutside operational restore window
Offload periodContinuouslyEvery four hours or on-demand

Backup chains: A backup chain consists of a full backup and any incremental backups taken after the full backup. Veeam considers a backup chain “sealed” when a new synthetic of an active full backup job completes.

Backup chains

Copy operations work in tandem with move operations. Once a backup chain is inactive, Veeam validates that data blocks reside in Amazon S3, and removes any data blocks residing on the performance tier, leaving behind only the metadata. In the event of a restore where the data blocks reside in Amazon S3, Veeam seamlessly recovers the data from Amazon S3, with no intervention required by the backup administrator.

Supported Amazon S3 storage classes and best practices

Veeam Backup & Replication Version 10 supports the ability to use the following Amazon S3 storage classes: Amazon S3 Standard, Amazon S3 Standard-Infrequent Access (S3 Standard-IA), and Amazon S3 One Zone-Infrequent Access (S3 One Zone-IA). Most customers choose to place their data in Amazon S3 Standard or Amazon S3 Standard-IA. These storage classes offer low latency, high throughput performance, durability designed for 99.999999999% (11 9’s) across multiple Availability Zones, and low storage cost.

Customers may also choose to use S3 One Zone-IA. S3 One Zone-IA is for data that is accessed less frequently, but requires rapid access when needed. Unlike other Amazon S3 storage classes that store data in a minimum of three Availability Zones, S3 One Zone-IA stores data in a single Availability Zone. This results in costs 20% less than S3 Standard-IA. S3 One Zone-IA is ideal for customers who want a lower-cost option for infrequently accessed data but do not require the availability and resilience of S3 Standard or S3 Standard-IA. It’s a good choice for storing secondary backup copies of on-premises data or easily re-creatable data.

Customers should weigh the cost differences based on their need for access and requirement for availability when planning to use Amazon S3 with Veeam Backup & Replication. This Veeam whitepaper helps you take these costs into consideration when planning and budgeting for using Amazon S3 storage with Veeam Backup & Replication.

Note: Capacity tier does not support Amazon S3 Glacier and Amazon S3 Glacier Deep Archive at this time. If these Amazon S3 storage classes are required, customers are encouraged to use AWS Storage Gateway’s Tape Gateway, which is covered in the next section. In addition, Veeam does not support S3 Lifecycle policies to transition or expire objects in Amazon S3 buckets used in the capacity tier. Enabling these policies could result in backup and restore job failures if needed data has expired. It is also important to ensure that sufficient available WAN bandwidth exists between your on-premises Veeam Backup server and Amazon S3. Sufficient WAN bandwidth ensures that backup and restore jobs can complete within a time window that is appropriate for your organization.

Veeam object immutability

Another enhancement to Veeam Backup & Replication Version 10 is the object immutability feature that leverages Amazon S3 Object Lock in compliance mode. This feature can be enabled when defining an Amazon S3 storage repository in Veeam, and it enables customers to make backups immutable for a given number of days. This is a popular feature in that your Veeam backups are stored in Amazon S3 using a write-once-read-many (WORM) model. This prevents backups from being deleted, modified, or overwritten – either accidentally or willingly, such as a ransomware attack. It’s important to note that Amazon S3 buckets must have Object Lock enabled at the time of S3 bucket creation. If there is a need to enable Object Lock on an existing bucket, please open a case with AWS Support who can assist you further.

AWS Storage Gateway: Tape Gateway

Veeam Backup & Replication Version 10 also supports the ability to back up directly to an AWS Storage Gateway in virtual tape library (VTL) mode. Tape Gateway presents a VTL consisting of virtual tape drives and a virtual media changer to Veeam using iSCSI. Using Tape Gateway enables customers to take advantage of the Amazon S3 Glacier and Amazon S3 Glacier Deep Archive storage classes. These storage classes can be useful when data is expected to be recovered infrequently and if you can tolerate non-immediate retrieval times. Retrieval times are typically between 3-5 hours for tapes archived in S3 Glacier, and typically within 12 hours for tapes archived in S3 Glacier Deep Archive. Customers also use Tape Gateway with Veeam to seamlessly replace using physical tapes on premises with virtual tapes in AWS without changing backup workflows in Veeam.

Tape Gateway is typically deployed on premises as a virtual or hardware appliance. Tape Gateway stores virtual tapes in service-managed S3 buckets and caches virtual tapes on premises for low-latency data access. Tape Gateway transitions virtual tapes between Amazon S3 and Amazon S3 Glacier or Amazon S3 Glacier Deep Archive when you eject and export virtual tapes from Veeam.

Using Veeam and AWS Storage Gateway's Tape Gateway to move data into the AWS Cloud

Customers like Reiden Technik AG have successfully used Veeam Backup & Replication with Tape Gateway to simplify their backup process and reduce their legacy backup infrastructure. By archiving virtual tapes in S3 Glacier Deep Archive, they also save on their storage costs:

We run an extensive IT environment that is constantly growing. With our old backup infrastructure, comprised of large external spinning disks, manual handling, and rotation of USB drives to an offsite vault, we hit our limits with regards to storage size. We found AWS Storage Gateway’s Tape Gateway capability to be the ideal solution for us as it integrates well with our VEEAM backup. The Tape Gateway installation was fast and easy, and we were able to automatically save and archive our entire infrastructure on a weekly basis. All our backups are now stored safely, securely, and in a more efficient and scalable manner. Tape Gateway is the perfect solution for us because after VEEAM ejects the virtual tape, the tape is then offline and inaccessible for anybody with access to our backup servers or VEEAM. With virtual tapes then archived to Amazon S3 Glacier Deep Archive, we are able to securely and durably store hundreds of terabytes of data at a very low price, allowing us to apply more budget toward business innovation rather than managing tapes. With Tape Gateway, we experienced easy integration, fully automated “offline” backups for peace of mind, no more manual physical transport of USB drives to our vault, direct integration with VEEAM Backup & Replication, and no additional licensing fees for separate VTL software.

Michael Müller, CIO – Reiden Technik AG

Disaster recovery in AWS

In addition to the low cost and durability of storing Veeam backups in Amazon S3, customers can also leverage native functionality within Veeam Backup & Replication to recover on-premises workloads. On-premises workloads can be recovered in AWS as Amazon EC2 instances as part of a broader DR strategy. Veeam Backup & Replication Version 10 enables customers to import Veeam backup metadata from Amazon S3 without the need to create and rescan the entire SOBR. This capability helps lower recovery time objectives (RTO).

Customers can choose to install Veeam Backup & Replication on an Amazon EC2 instance at the time of disaster. They can also choose to preinstall Veeam Backup & Replication on an EC2 instance and leave the instance in a powered-down state, powering on only for occasional operating system and Veeam updates. This enables customers to have a true “pilot light” DR strategy with little effort. As with any DR strategy, we encourage customers to regularly test their DR plans to ensure that the outcomes match the expectations of your organization, and iterate as necessary.

When performing a DR test using a Veeam Backup & Replication server in AWS, and when the object storage repository contains backups of on-premises systems, it is important to ensure that the on-premises Veeam backup server does not have any active jobs running while the Veeam Backup Server in AWS is accessing backup data in Amazon S3. Therefore, it is recommended to shut down the on-premises Veeam backup server to ensure that any testing does not negatively impact on-premises backup jobs, which could occur if both Veeam Servers are writing to the same Amazon S3 Bucket at once.

Customers can choose to install Veeam Backup and Replication on an Amazon EC2 instance at the time of disaster, or preinstall on a powered-down EC2 instance

Veeam Backup for Microsoft Office 365

Customers have requested the ability to leverage Amazon S3 to protect their Office 365 backups outside of their Office 365 environment. Veeam Backup for Microsoft Office 365 enables customers to protect their Microsoft Office 365 data including Microsoft Exchange, SharePoint, OneDrive, and Teams by storing Microsoft Office 365 data in Amazon S3. This enables customers an additional air-gapped layer of protection if data corruption or data loss occurs. Customers can choose to store data in Amazon S3 Standard or S3 Standard-IA. S3 Standard-IA would be more appropriate for backups that require longer retention periods and lower probability of restore.

Conclusion

In this blog post, we discussed how customers can use Veeam Backup & Replication with different Amazon S3 storage classes and AWS Storage Gateway. We also covered use cases and differences between them. In addition, we’ve shown how customers can leverage Veeam Backup & Replication to provide DR functionality in AWS by recovering to Amazon EC2 instances.

The information contained in this post also showed how to plan for extending your on-premises Veeam Backup & Replication environment into AWS using different approaches. This enables you to reduce your on-premises backup infrastructure, which helps to reduce costs and the undifferentiated heavy lifting involved in operating and maintaining on-premises backup infrastructure. Veeam integrations with AWS also provide additional benefits such as leveraging S3 Object Lock to guard against events like ransomware attacks.

Thanks for reading this blog post! If you have any comments or questions, please leave them in the comments section.

Additional resources

The following links provide some additional resources for further reading on the topics covered in this blog post:

The content and opinions in this post are those of the third-party author and AWS is not responsible for the content or accuracy of this post.

Источник: https://aws.amazon.com/blogs/storage/using-veeam-with-aws-storage-services-to-store-off-site-backups/

How to properly load balance your backup infrastructure

How to properly load balance your backup infrastructure

Veeam Backup & Replication is known for ease of installation and a moderate learning curve. It is something that we take as a great achievement, but as we see in our support practice, it can sometimes lead to a “deploy and forget” approach, without fine-tuning the software or learning the nuances of its work. In our previous blog posts, we examined tape configuration considerations and some common misconfigurations. This time, the blog post is aimed at giving the reader some insight on a Veeam Backup & Replication infrastructure, how data flows between the components, and most importantly, how to properly load balance backup components so that the system can work stably and efficiently.

Overview of a Veeam Backup & Replication infrastructure

Veeam Backup & Replication is a modular system. This means that Veeam as a backup solution consists of a number of components, each with a specific function. Examples of such components are the Veeam server itself (as the management component), proxy, repository, WAN accelerator and others. Of course, several components can be installed on a single server (provided that it has sufficient resources) and many customers opt for all-in-one installations. However, distributing components can give several benefits:

  • For customers with branch offices, it is possible to localize the majority of backup traffic by deploying components locally.
  • It allows to scale out easily. If your backup window increases, you can deploy an additional proxy. If you need to expand your backup repository, you can switch to scale-out backup repository and add new extents as needed.
  • You can achieve a High Availability for some of the components. For example, if you have multiple proxies and one goes offline, the backups will still be created.

Such system can only work efficiently if everything is balanced. An unbalanced backup infrastructure can slow down due to unexpected bottlenecks or even cause backup failures because of overloaded components.

Let’s review how data flows in a Veeam infrastructure during a backup (we're using a vSphere environment in this example):

All data in Veeam Backup & Replication flows between source and target transport agents. Let’s take a backup job as an example: a source agent is running on a backup proxy and its job is to read the data from a datastore, apply compression and source-side deduplication and send it over to a target agent. The target agent is running directly on a Windows/Linux repository or a gateway if a CIFS share is used. Its job is to apply a target-side deduplication and save the data in a backup file (.VKB, .VIB etc).

That means there are always two components involved, even if they are essentially on the same server and both must be taken into account when planning the resources.

Tasks balancing between proxy and repository

To start, we must examine the notion of a “task.” In Veeam Backup & Replication, a task is equal to a VM disk transfer. So, if you have a job with 5 VMs and each has 2 virtual disks, there is a total of 10 tasks to process. Veeam Backup & Replication is able to process multiple tasks in parallel, but the number is still limited.

If you go to the proxy properties, on the first step you can configure the maximum concurrent tasks this proxy can process in parallel:

For normal backup operations, a task on the repository side also means one virtual disk transfer.

On the repository side, you can find a very similar setting:

For normal backup operations, a task on the repository side also means one virtual disk transfer.

This brings us to our first important point: it is crucial to keep the resources and number of tasks in balance between proxy and repository.  Suppose you have 3 proxies set to 4 tasks each (that means that on the source side, 12 virtual disks can be processed in parallel), but the repository is set to 4 tasks only (that is the default setting). That means that only 4 tasks will be processed, leaving idle resources.

The meaning of a task on a repository is different when it comes to synthetic operations (like creating synthetic full). Recall that synthetic operations do not use proxies and happen locally on a Windows/Linux repository or between a gateway and a CIFS share. In this case for normal backup chains, a task is a backup job (so 4 tasks mean that 4 jobs will be able to generate synthetic full in parallel), while for per-VM backup chains, a task is still a VM (so 4 tasks mean that repo can generate 4 separate VBKs for 4 VMs in parallel). Depending on the setup, the same number of tasks can create a very different load on a repository! Be sure to analyze your setup (the backup job mode, the job scheduling, the per-VM option) and plan resources accordingly.

Note that, unlike for a proxy, you can disable the limit for number of parallel tasks for a repository. In this case, the repository will accept all incoming data flows from proxies. This might seem convenient at first, but we highly discourage from disabling this limitation, as it may lead to overload and even job failures. Consider this scenario: a job has many VMs with a total of 100 virtual disks to process and the repository uses the per-VM option. The proxies can process 10 disks in parallel and the repository is set to the unlimited number of tasks. During an incremental backup, the load on the repository will be naturally limited by proxies, so the system will be in balance. However, then a synthetic full starts. Synthetic full does not use proxies and all operations happen solely on the repository. Since the number of tasks is not limited, the repository will try to process all 100 tasks in parallel! This will require immense resources from the repository hardware and will likely cause an overload.

Considerations when using CIFS share

If you are using a Windows or Linux repository, the target agent will start directly on the server.  When using a CIFS share as a repository, the target agent starts on a special component called a “gateway,” that will receive the incoming traffic from the source agent and send the data blocks to the CIFS share. The gateway must be placed as close to the system sharing the folder over SMB as possible, especially in scenarios with a WAN connection. You should not create topologies with a proxy/gateway on one site and CIFS share on another site “in the cloud” — you will likely encounter periodic network failures.

The same load balancing considerations described previously apply to gateways as well. However, the gateway setup requires an additional attention because there are 2 options available — set the gateway explicitly or use an automatic selection mechanism:

Any Windows “managed server” can become a gateway for a CIFS share. Depending on the situation, both options can come handy. Let’s review them.

You can set the gateway explicitly. This option can simplify the resource management — there can be no surprises as to where the target agent will start. It is recommended to use this option if an access to the share is restricted to specific servers or in case of distributed environments — you don’t want your target agent to start far away from the server hosting the share!

Things become more interesting if you choose Automatic selection. If you are using several proxies, automatic selection gives ability to use more than one gateway and distribute the load. Automatic does not mean random though and there are indeed strict rules involved.

The target agent starts on the proxy that is doing the backup. In case of normal backup chains, if there are several jobs running in parallel and each is processed by its own proxy, then multiple target agents can start as well. However, within a single job, even if the VMs in the job are processed by several proxies, the target agent will start only on one proxy, the first to start processing. For per-VM backup chains, a separate target agent starts for each VM, so you can get the load distribution even within a single job.

Synthetic operations do not use proxies, so the selection mechanism is different: the target agent starts on the mount server associated with the repository (with an ability to fail over to Veeam server if the mount server in unavailable). This means that the load of synthetic operations will not be distributed across multiple servers. As mentioned above, we discourage from setting the number of tasks to unlimited — that can cause a huge load spike on the mount/Veeam server during synthetic operations.

Additional notes

Scale-out backup repository. SOBR is essentially a collection of usual repositories (called extents). You cannot point a backup job to a specific extent, only to SOBR, however extents retain some of settings, including the load control. So what was discussed about standalone repositories, pertains to SOBR extents as well. SOBR with per-VM option (enabled by default), the “Performance” placement policy and backup chains spread out across extents will be able to optimize the resource usage.

Backup copy. Instead of a proxy, source agents will start on the source repository. All considerations described above apply to source repositories as well (although in case of Backup Copy Job, synthetic operations on a source repository are logically not possible). Note that if the source repository is a CIFS share, the source agents will start on the mount server (with a failover to Veeam server).

Deduplication appliances. For DataDomain, StoreOnce (and possibly other appliances in the future) with Veeam integration enabled, the same considerations apply as for CIFS share repositories. For a StoreOnce repository with source-side deduplication (Low Bandwidth mode) the requirement to place gateway as close to the repository as possible does not apply — for example, a gateway on one site can be configured to send data to a StoreOnce appliance on another site over WAN.

Proxy affinity. A feature added in 9.5, proxy affinity creates a “priority list” of proxies that should be preferred when a certain repository is used.

If a proxy from the list is not available, a job will use any other available proxy. However, if the proxy is available, but does not have free task slots, the job will be paused waiting for free slots. Even though the proxy affinity is a very useful feature for distributed environments, it should be used with care, especially because it is very easy to set and forget about this option. Veeam Support encountered cases about “hanging” jobs which came down to the affinity setting that was enabled and forgotten about. More details on proxy affinity.

Conclusion

Whether you are setting up your backup infrastructure from scratch or have been using Veeam Backup & Replication for a long time, we encourage you to review your setup with the information from this blog post in mind. You might be able to optimize the use of resources or mitigate some pending risks!

Источник: https://www.rackscale.sk/blog/how-to-properly-load-balance-your-backup-infrastructure

Veeam Backup & Replication Enterprise Plus 11.0.1.1261 + Activator Fullversion

 Free Download Veeam Backup & Replication 11 full version standalone offline installer for Windows it is a complete solution designed specifically for backing up virtual machines (VMs) and ensuring data availability.

Veeam Backup & Replication ensures fast, efficient and reliable recovery of virtualized applications and data. The solution combines backup and replication capabilities for VMware vSphere and Microsoft Hyper-V.

Overview of Veeam Backup & Replication 11 Benefits

This program helps businesses achieve comprehensive data protection for ALL workloads — virtual, physical and cloud-based workloads. With a single console, achieve fast, flexible and reliable backup, recovery and replication of all applications and data.

It delivers Intelligent Data Management for ALL your virtual, physical and cloud-based workloads. Through a single management console, you can manage fast, flexible and reliable backup, recovery and replication of all your applications and data to eliminate legacy backup solutions forever.

Download Version




Download Only

Overview of Features

  • Fast, reliable application-aware, image-based backups
  • Hardware and cloud-agnostic
  • Virtual, physical & cloud
  • Unlimited capacity and cost savings for long-term data retention on object storage with Veeam Cloud Tier
  • Enterprise application support for Veeam Plug-ins for SAP HANA and Oracle RMAN
  • Lower RPOs and faster backups to the leading storage providers
  • 2-in-1: backup and replication
  • Advanced replication and failover for Disaster Recovery
  • Built-in WAN Acceleration to get backups and replicas off site fast
  • Fully-integrated, cloud-based DR replication and fast, secure cloud backup with Veeam Cloud Connect through a service provider
  • Recover individual files effortlessly with Instant VM and File-level Recovery
  • Easy portability and recovery to AWS, Azure and Azure Stack with Veeam Cloud Mobility
  • Fast, item-level recovery and eDiscovery for Microsoft Exchange, SharePoint, and Active Directory
  • Transaction-level restore of Oracle databases and SQL Server databases
  • Advanced self-service controls

Veeam Backup & Replication 11 applications:

  • Veeam_Backup & Replication
  • Veeam_Backup Enterprise Manager
  • Veeam_Cloud Backup
  • Veeam_ONE
  • Veeam_ONE Client

Version and Updates

  • 10.0.0.4461 (10.0.0.4461 P1, 10.0.0.4461 P2, 10.0.1.4854, 10.0.1.4854 P20201202)
Veeam Backup & Replication Enterprise Plus 11.0.1.1261 + Activator Fullversion

 
 

Источник: https://www.zuketcreation.net/veeam-backup-replication-enterprise-plus-11-0-1-1261-activator-fullversion
VEEAM

VEEAM

Veeam Software is a privately held US-based information technology company that develops backup, disaster recovery and intelligent data management software for virtual, physical and multi-cloud infrastructures.

Available solutions


LinkSourceCompatibilityType, TechnologyCreated UpdatedRating
Template VEEAM Backup & Replication
This template use the VEEAM Backup & Replication PowerShell Cmdlets to discover and manage VEEAM Backup jobs, Veeam BackupSync, Veeam Tape Job, Veeam Endpoint Backup Jobs, All Repositories and Veeam Services.
           
github.com/romainsi/zabbix-VEEAM_B-R
share.zabbix.com/veeam-backup-recovery-jobs-trapper
Veeam Backup & Replication by SMTP
This Veeam Backup & Replication use email and not Powershell snippet. It is as efficient (or more) as other method of integration with Zabbix and it requires a lot less ressources. It monitors even Backup Database backup (which others do not). Using a specific script it can be applied to Free Agents...
  

share.zabbix.com/veeam-backup-replication-by-smtp

This template use the VEEAM Backup & Replication PowerShell Cmdlets to discover and manage VEEAM Backup jobs, Veeam BackupSync, Veeam Tape Job, Veeam Endpoint Backup Jobs, All Repositories and Veeam Services.
  

share.zabbix.com/veeam-agents-for-microsoft-windows


+ Propose new solution

Источник: https://www.zabbix.com/integrations/veeam

Veeam Backup & Replication 10 Free Download

Veeam Backup & Replication 10 Free Download New and latest Version for Windows. It is full offline installer standalone setup of Veeam Backup & Replication 10 Free Download for compatible version of windows. Program was checked and installed manually before uploading by our staff, it is fully working version without any problems.

Veeam Backup & Replication 10 Overview

This program helps businesses achieve comprehensive data protection for ALL workloads  virtual, physical and cloud-based workloads. With a single console, achieve fast, flexible and reliable backup, recovery and replication of all applications and data. You can also download Macrium Reflect 7.2.4732 Server Plus.

It delivers Intelligent Data Management for ALL your virtual, physical and cloud-based workloads. Through a single management console, you can manage fast, flexible and reliable backup, recovery and replication of all your applications and data to eliminate legacy backup solutions forever. You also may like to download Stellar Data Recovery Professional 9.

Features of Veeam Backup & Replication 10

Below are some amazing features you can experience after installation of Veeam Backup & Replication 10 Free Download please keep in mind features may vary and totally depends if your system support them.

  • Fast, reliable application-aware, image-based backups
  • Hardware and cloud-agnostic
  • Virtual, physical & cloud
  • Unlimited capacity and cost savings for long-term data retention on object storage with Veeam Cloud Tier
  • Enterprise application support for Veeam Plug-ins for SAP HANA and Oracle RMAN
  • Lower RPOs and faster backups to the leading storage providers
  • 2-in-1: backup and replication
  • Advanced replication and failover for Disaster Recovery
  • Built-in WAN Acceleration to get backups and replicas off site fast
  • Fully-integrated, cloud-based DR replication and fast, secure cloud backup with Veeam Cloud Connect through a service provider
  • Recover individual files effortlessly with Instant VM and File-level Recovery
  • Easy portability and recovery to AWS, Azure and Azure Stack with Veeam Cloud Mobility
  • Fast, item-level recovery and eDiscovery for Microsoft Exchange, SharePoint, and Active Directory
  • Transaction-level restore of Oracle databases and SQL Server databases
  • Advanced self-service controls

System Requirements for Veeam Backup & Replication 10

Before you install Veeam Backup & Replication 10 Free Download you need to know if your pc meets recommended or minimum system requirements:

Operating system 

  • CPU: x86-64 processor memory: 2 GB RAM
  • Disk space: 150 MB for product installation
  • Network: 1 Mbps or faster
  • System firmware: BIOS or UEFI
  • Drive encryption: Microsoft BitLocker (optional)
  • OS: Both 64-bit and 32-bit versions of Microsoft Windows client and server operating systems are supported. For a complete list, please refer to the User Guide.

Veeam Backup & Replication 10 Technical Setup Details

  • Software Full Name: Veeam Backup & Replication 10
  • Setup File Name: PcWonderland.com_Veeam_Backup_Replication_10.zip
  • Size: 3.4 GB (because of constant update from back-end file size or name may vary)
  • Setup Type: Offline Installer / Full Standalone Setup
  • Compatibility Architecture: 64Bit (x64) 32Bit (x86)

Veeam Backup & Replication 10 Free Download

Click on below button to start Veeam Backup & Replication 10 Free Download. This is complete offline installer and standalone setup for Veeam Backup & Replication 10. This would be compatible with compatible version of windows.

How to Install Veeam Backup & Replication 10

  • Extract the zip file using WinRAR or WinZip or by default Windows command.
  • Open Installer and accept the terms and then install program.
  • If you have any problem you can get help in Request Section.

How to Download Veeam Backup & Replication 10

  1. Click download button below and you will be redirected to next page.
  2. On next page you need to wait for 10 seconds to get download button.
  3. Click on download now button to start your download.
  4. Enjoy and bookmark our website, visit us daily for latest and quality downloads.
  5. If you have any software request, you can post it in our Request Section.

Password is always: pcwonderland.com

Источник: https://pcwonderland.com/veeam-backup-replication-10-free-download/

Backup to Azure with Veeam

This article helps you integrate a Veeam infrastructure with Azure Blob storage. It includes prerequisites, considerations, implementation, and operational guidance. This article addresses using Azure as an offsite backup target and a recovery site if a disaster occurs, which prevents normal operation within your primary site.

Note

Veeam also offers a lower recovery time objective (RTO) solution, Veeam Backup & Replication with support for Azure VMware Solution workloads. This solution lets you have a standby VM that can help you recover more quickly in the event of a disaster in an Azure production environment. Veeam also offers Direct Restore to Microsoft Azure and other dedicated tools to back up Azure and Office 365 resources. These capabilities are outside the scope of this document.

Reference architecture

The following diagram provides a reference architecture for on-premises to Azure and in-Azure deployments.

Veeam to Azure reference architecture diagram.

Your existing Veeam deployment can easily integrate with Azure by adding an Azure storage account, or multiple accounts, as a cloud backup repository. Veeam also allows you to recover backups from on-premises within Azure giving you a recovery-on-demand site in Azure.

Veeam interoperability matrix

WorkloadGPv2 and Blob StorageCool tier supportArchive tier supportData Box Family support
On-premises VMs/datav10av10aN/A10a*
Azure VMsv10av10aN/A10a*
Azure Blobv10av10aN/A10a*
Azure Filesv10av10aN/A10a*

Veeam has offered support for above Azure features in older versions of their product as well, for optimal experience leveraging the latest product version is strongly recommended.

*Veeam Backup and Replication support REST API only for Azure Data Box. Therefore, Azure Data Box Disk is not supported. Please see details for Data Box support here.

Before you begin

A little upfront planning will help you use Azure as an offsite backup target and recovery site.

Get started with Azure

Microsoft offers a framework to follow to get you started with Azure. The Cloud Adoption Framework (CAF) is a detailed approach to enterprise digital transformation and comprehensive guide to planning a production grade cloud adoption. The CAF includes a step-by-step Azure Setup Guide to help you get up and running quickly and securely. You can find an interactive version in the Azure portal. You'll find sample architectures, specific best practices for deploying applications, and free training resources to put you on the path to Azure expertise.

Consider the network between your location and Azure

Whether using cloud resources to run production, test and development, or as a backup target and recovery site, it's important to understand your bandwidth needs for initial backup seeding and for ongoing day-to-day transfers.

Azure Data Box provides a way to transfer your initial backup baseline to Azure without requiring more bandwidth. This is useful if the baseline transfer is estimated to take longer than you can tolerate. You can use the Data Transfer estimator when you create a storage account to estimate the time required to transfer your initial backup.

Shows the Azure Storage data transfer estimator in the portal.

Remember, you'll require enough network capacity to support daily data transfers within the required transfer window (backup window) without impacting production applications. This section outlines the tools and techniques that are available to assess your network needs.

Determine how much bandwidth you'll need

Multiple assessment options are available to determine change rate and total backup set size for the initial baseline transfer to Azure. Here are some examples of assessment and reporting tools:

Determine unutilized internet bandwidth

It's important to know how much typically unutilized bandwidth (or headroom) you have available on a day-to-day basis. This helps you assess whether you can meet your goals for:

  • initial time to upload when you're not using Azure Data Box for offline seeding
  • completing daily backups based on the change rate identified earlier and your backup window

Use the following methods to identify the bandwidth headroom that your backups to Azure are free to consume.

Choose the right storage options

When you use Azure as a backup target, you'll make use of Azure Blob storage. Blob storage is Microsoft's object storage solution. Blob storage is optimized for storing massive amounts of unstructured data, which is data that does not adhere to any data model or definition. Additionally, Azure Storage is durable, highly available, secure, and scalable. You can select the right storage for your workload to provide the level of resiliency to meet your internal SLAs. Blob storage is a pay-per-use service. You're charged monthly for the amount of data stored, accessing that data, and in the case of cool and archive tiers, a minimum required retention period. The resiliency and tiering options applicable to backup data are summarized in the following tables.

Blob storage resiliency options:

Locally-redundantZone-redundantGeo-redundantGeo-zone-redundant
Effective # of copies3366
# of availability zones1324
# of regions1122
Manual failover to secondary regionN/AN/AYesYes

Blob storage tiers:

Hot tierCool tierArchive tier
Availability99.9%99%Offline
Usage chargesHigher storage costs, Lower access, and transaction costsLower storage costs, higher access, and transaction costsLowest storage costs, highest access, and transaction costs
Minimum data retention requiredNA30 days180 days
Latency (time to first byte)MillisecondsMillisecondsHours

Sample backup to Azure cost model

With pay-per-use can be daunting to customers who are new to the cloud. While you pay for only the capacity used, you do also pay for transactions (read and or writes) and egress for data read back to your on-premises environment when Azure Express Route direct local or Express Route unlimited data plan are in use where data egress from Azure is included. You can use the Azure Pricing Calculator to perform "what if" analysis. You can base the analysis on list pricing or on Azure Storage Reserved Capacity pricing, which can deliver up to 38% savings. Here's an example pricing exercise to model the monthly cost of backing up to Azure. This is only an example. Your pricing may vary due to activities not captured here.

Cost factorMonthly cost
100 TB of backup data on cool storage$1556.48
2 TB of new data written per day x 30 days$42 in transactions
Monthly estimated total$1598.48
------------------
One time restore of 5 TB to on-premises over public internet$527.26

Note

This estimate was generated in the Azure Pricing Calculator using East US Pay-as-you-go pricing and is based on the Veeam default of 512 kb chunk size for WAN transfers. This example may not be applicable towards your requirements.

Implementation guidance

This section provides a brief guide for how to add Azure Storage to an on-premises Veeam deployment. For detailed guidance and planning considerations, we recommend you take a look at the following Veeam Guidance for their Capacity Tier.

  1. Open the Azure portal, and search for Storage Accounts. You can also click on the default service icon.

    Shows adding a storage accounts in the Azure portal.

    Shows where you've typed storage in the search box of the Azure portal.

  2. Select Create to add an account. Select or create a resource group, provide a unique name, choose the region, select Standard performance, always leave account kind as Storage V2, choose the replication level which meets your SLAs, and the default tier your backup software will apply. An Azure Storage account makes hot, cool, and archive tiers available within a single Veeam Backup & Replication Offline Installer and Veeam policies allow you to use multiple tiers to effectively manage the lifecycle of your data.

    Shows storage account settings in the portal

  3. Keep the default networking and data protection options for now. Do not enable Soft Delete for Storage Accounts storing Veeam capacity tiers.

  4. Next, we recommend the default settings from the Advanced screen for backup to Azure use cases.

    Shows Advanced settings tab in the portal.

  5. Add tags for organization if you use tagging, and create your account.

  6. Two quick steps are all that are now required before you can add the account to your Veeam environment. Navigate to the account you created in the Azure portal and select Containers under the Blob service menu. Add a container and choose a meaningful name. Then, navigate to the Access keys item under Settings and copy the Storage account name and one of the two access keys. You will need the container name, account name, and access key in the next steps.

    Shows container creation in the portal.

    Shows access key settings in the portal.

    Note

    Veeam Backup and Replication offers additional options to connect to Azure. For the use case of this article, using Microsoft Azure Blob Storage as a backup target, using the above method is the recommended best practice.

  7. (Optional) You can add more layers of security to your deployment.

    1. Configure role-based access to limit who can make changes to your storage account. For more information, see Built-in roles for management operations.

    2. Restrict access to the account to specific network segments with storage firewall settings to prevent access attempts from outside your corporate network.

      Shows storage firewall settings in the portal.

    3. Set Veeam Backup & Replication Offline Installer delete lock on the account to prevent accidental deletion of the storage account.

      Resource Lock

    4. Configure additional security best practices.

  8. In the Veaam Backup and Replication Management Console, navigate to Backup Infrastructure -> right-click in the overview pane and select Add Veeam Backup & Replication Offline Installer Repository to open the configuration wizard. In the dialog box, select Object storage -> Microsoft Azure Blob Storage -> Azure Blob Storage.

    Shows selecting object storage in the Veeam Repository Wizard.

    Shows selecting Microsoft Azure Blob Storage in the Veeam Repository Wizard.

    Shows selecting Azure Blob Storage in the Veeam Repository Wizard.

  9. Next, specify a name and a description of your new Blob storage repository.

    Shows typing a name for the repository in the Veeam Repository Wizard.

  10. In the next step, add the credentials to access your Azure storage account. Select Microsoft Azure Storage Account in the Cloud Credential Manager, and enter your storage account name and access key. Select Azure Global in the region selector, and any gateway server if applicable.

    Shows specifying an account in the Veeam Repository Wizard.

    Note

    If you choose not to use a Veeam gateway server, make sure that all scale-out repository extents have direct internet access.

  11. On the container register, select your Azure Storage container and select or create a folder to store your backups in. You can also define a soft limit on the overall storage capacity to be used by Veeam, which is recommended. Review the displayed information in the summary section and complete the configuration tool. You can now select the new repository in your backup job configuration.

    Shows specifying a container in the Veeam Repository Wizard.

    Shows creating a folder in the Veeam Repository Wizard.

Operational guidance

Azure alerts and performance monitoring

It is advisable to monitor both your Azure resources and Veeam's ability to leverage them as you would with any storage target you rely on to store your backups. A combination of Azure Monitor and Veeam's monitoring capabilities (the Statistics tab in the Jobs node of the Veeam Management Console or more advanced options like Lonely screen free One Reporter) will help you keep your environment healthy.

Azure portal

Azure provides a robust monitoring solution in the form of Azure Monitor. You can configure Azure Monitor to track Azure Storage capacity, transactions, availability, authentication, and more. The full reference of metrics tracked may be found here. A few useful metrics to track are BlobCapacity - to make sure you remain below the maximum storage account capacity limit, Ingress and Egress - to track the amount of data being written to and read from your Azure storage account, and SuccessE2ELatency - to track the roundtrip time for requests to and from Azure Storage and your MediaAgent.

You can also create log alerts to track Azure Storage service health and view the Azure status dashboard at any time.

Veeam reporting

How to open support cases

When you need help with your backup to Azure solution, you should open a case with both Veeam and Azure. This helps our support organizations to collaborate, if necessary.

To open a case with Veeam

On the Veeam customer support site, sign in, and open a case.

To understand the support options available to you by Veeam, see the Veeam Customer Support Policy.

You may also call to open a case: Worldwide support numbers

To open a case with Azure

In the Azure portal search for Veeam Backup & Replication Offline Installer in the search bar at the top. Select Help + support -> New Support Request.

Note

When you open a case, be specific that you need assistance with Azure Storage or Azure Networking. Do not specify Azure Backup. Azure Backup is the name of an Azure service and your case will be routed incorrectly.

Links to relevant Veeam documentation

See the following Veeam documentation for further detail:

Marketplace offerings

You can continue to use the Veeam solution you know and trust to protect your workloads running on Azure. Veeam has made it easy to deploy their solution in Azure and protect Azure Virtual Machines and many other Azure services.

Next steps

See the following resources on the Veeam website for information about specialized usage scenarios:

Источник: https://docs.microsoft.com/en-us/azure/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/veeam/veeam-solution-guide

Using Veeam with AWS Storage services to store offsite backups

Many customers are using Veeam Backup & Replication to protect their on-premises infrastructure and want to reduce the amount of physical backup infrastructure that they need to purchase and maintain. They also want to ensure that their backups reside in highly durable, cost effective storage. AWS Storage services such as Amazon S3, AWS Storage Gateway, and AWS Snowball Edge seamlessly integrate with Veeam Backup & Replication to meet these needs.

Veeam Backup & Replication enables customers to automatically tier backups to Amazon S3 to help reduce their reliance and costs associated with more expensive on-premises backup storage. Initially released in January 2019 in version 9.5 Update 4, Veeam Backup & Replication has been used by customers such as Best Friends Animal Society (case study) to enhance their DR strategy while providing cost savings. In February 2020, Veeam released Veeam Backup & Replication Version 10, adding additional functionality to capacity tier. Capacity tier is an additional tier of storage that can be attached to a scale-out backup repository.

In this blog post, we review the options and best practices available to Veeam customers looking to integrate with AWS Storage services based on knowledge learned both in the lab and in the field. In Veeam Backup & Replication Offline Installer, we discuss strategies to help you leverage Veeam Backup & Replication to recover your on-premises workloads in AWS as Amazon EC2 instances for disaster recovery (DR) purposes. By the end of this post, you should have a better understanding of how the integration between Veeam Backup & Replication with AWS Storage services works. You will also have information to decide on which approach would work best for your organizations use case, including any caveats to watch out for when implementing these integrations.

Veeam concepts

Let’s look into some of the concepts involved with Veeam Backup & Replication.

Scale-out backup repository (SOBR): A SOBR is a logical entity that consists of one or more backup repositories that are configured as tiers. A SOBR is used as a single target for backup and copy jobs. Customers must configure a SOBR that contains a performance tier that provides fast access to data with locally hosted backup repositories as direct-attach block storage, NAS storage, or a deduplication appliance. The SOBR also enables customers to define a capacity tier that is useful for long-term storage, where Amazon S3 is used as the object storage repository.

Veeam customers can also leverage AWS Snowball Edge as an object storage repository to seed large initial backups to Amazon S3. Snowball Edge is a small, rugged, and secure portable storage and edge computing device used for data collection, processing, and migration. Snowball Edge devices are purpose-built for moving multiple terabytes of data offline to AWS to overcome the challenge of limited bandwidth.Snowball Edge encrypts all data at rest with 256-bit encryption with keys provided by the customer using the AWS Key Management Service (AWS KMS). This can be helpful for customers with large volumes of on-premises backups who may not have the WAN bandwidth to complete the data seeding within an acceptable amount of time. Veeam customers who want to use Snowball Edge must be running Veeam Backup & Replication 10a, which was released in July 2020. For more information on how to set up Snowball Edge as an object storage repository, please review the relevant Veeam documentation.

Scale-out backup repository (SOBR)

Copy and move operations: Customers can choose to configure their capacity tier to have Veeam backups sent to Amazon S3 in two ways. Customers can immediately copy backups to Amazon S3 after the backup job has completed. Alternatively, they can move backups from the performance tier to Amazon S3 once the backup chain has been sealed and it is outside of a defined operational restore window.

Copy operation to capacity tierMove operation to capacity tier
Applies toAny backup (full, incremental, etc.)Sealed backup chains
Offload timeUpon completion of backup jobOutside operational restore window
Offload periodContinuouslyEvery four hours or on-demand

Backup chains: A backup chain consists of a full backup and any incremental backups taken after the full backup. Veeam considers a backup chain “sealed” when a new synthetic of an active full backup job completes.

Backup chains

Copy operations work in tandem with move operations. Once a backup chain is inactive, Veeam validates that data blocks reside in Amazon S3, and removes any data blocks residing on the performance tier, leaving behind only the metadata. In the event of a restore where the data blocks reside in Amazon S3, Veeam seamlessly recovers the data from Amazon S3, with no intervention required by the backup administrator.

Supported Amazon S3 storage classes and best practices

Veeam Backup & Replication Version 10 supports the ability to use the following Amazon S3 storage classes: Amazon S3 Standard, Amazon S3 Standard-Infrequent Access (S3 Standard-IA), and Amazon S3 One Zone-Infrequent Access (S3 One Zone-IA). Most customers choose to place their data in Amazon S3 Standard or Amazon S3 Standard-IA. These storage classes offer low latency, high throughput performance, durability designed for 99.999999999% (11 9’s) across multiple Availability Zones, and low storage cost.

Customers may also choose to use S3 Veeam Backup & Replication Offline Installer Zone-IA. S3 One Zone-IA is for data that is accessed less frequently, but requires rapid access when needed. Unlike other Amazon S3 storage classes that store data in a minimum of three Availability Zones, S3 One Zone-IA stores data in a single Availability Zone. This results in costs 20% less than S3 Standard-IA. S3 One Zone-IA is ideal for customers who want a lower-cost option for infrequently accessed data but do not require the availability and resilience of S3 Standard or S3 Standard-IA. It’s a good choice for storing secondary backup copies of on-premises data or easily re-creatable data.

Customers should weigh the cost differences based on their need for access and requirement for availability when planning to use Amazon S3 with Veeam Backup & Replication. This Veeam whitepaper helps you take these costs into consideration when planning and budgeting for using Amazon S3 storage with Veeam Backup & Replication.

Note: Capacity tier does not support Amazon S3 Glacier and Amazon S3 Glacier Deep Archive at this time. If these Amazon S3 storage classes are required, customers are encouraged to use AWS Storage Gateway’s Tape Gateway, which is covered in the next section. In addition, Veeam does not support S3 Lifecycle policies to transition or expire objects in Amazon S3 buckets used in the capacity tier. Enabling these policies could result in backup and restore job failures if needed data has expired. It is also important to ensure that sufficient available WAN bandwidth exists between your on-premises Veeam Backup server and Amazon S3. Sufficient WAN bandwidth ensures that backup and restore jobs can complete within a time window that is appropriate for your organization.

Veeam object immutability

Another enhancement to Veeam Backup & Replication Version 10 is the object immutability feature that leverages Amazon S3 Object Lock in compliance mode. This feature can be enabled when defining an Amazon S3 storage repository in Veeam, and it enables customers to make backups immutable for a given number of days. This is a popular feature in that your Veeam backups are stored in Amazon S3 using a write-once-read-many (WORM) model. This prevents backups from being deleted, modified, or overwritten – either accidentally or willingly, such as a ransomware attack. It’s important to note that Amazon S3 buckets must have Object Lock enabled at the time of S3 bucket creation. If there tenorshare ultdata free a need to enable Object Lock on an existing bucket, please open a case with AWS Support who can assist you further.

AWS Storage Gateway: Tape Gateway

Veeam Backup & Replication Version 10 also supports the ability to back up directly to an AWS Storage Gateway in virtual tape library (VTL) mode. Tape Gateway presents a VTL consisting of virtual tape drives and a virtual media changer to Veeam using iSCSI. Using Tape Gateway enables customers to take advantage of the Amazon S3 Glacier and Amazon S3 Glacier Deep Archive storage classes. These storage classes can be useful when data is expected to be recovered infrequently and if you can tolerate non-immediate retrieval times. Retrieval times are typically between 3-5 hours for tapes archived in S3 Glacier, and typically within 12 hours for tapes archived in S3 Glacier Deep Archive. Customers also use Tape Gateway with Veeam to seamlessly replace using physical tapes on premises with virtual tapes in AWS without changing backup workflows in Veeam.

Tape Gateway is typically deployed on premises as a virtual or hardware appliance. Tape Gateway stores virtual tapes in service-managed S3 buckets and caches virtual tapes on premises for low-latency data access. Tape Gateway transitions virtual tapes between Veeam Backup & Replication Offline Installer S3 and Amazon S3 Glacier or Amazon S3 Glacier Deep Archive when you eject and export virtual tapes from Veeam.

Using Veeam and AWS Storage Gateway's Tape Gateway to move data into the AWS Cloud

Customers like Reiden Technik AG have successfully used Veeam Backup & Replication with Tape Gateway to simplify their backup process and reduce their legacy backup infrastructure. By archiving virtual tapes in S3 Glacier Deep Archive, they also save on their storage costs:

We run an extensive IT environment that is constantly growing. With our old backup infrastructure, comprised of large external spinning disks, manual handling, and rotation of USB drives to an offsite vault, we hit our limits with regards to storage size. We found AWS Storage Gateway’s Tape Gateway capability to be the ideal solution for us as it integrates well with our VEEAM backup. The Tape Gateway installation was fast and easy, and we were able to automatically save and archive our entire infrastructure on a weekly basis. All our backups are now stored safely, securely, and in a more efficient and scalable manner. Tape Gateway is the perfect solution for us because after VEEAM ejects the virtual tape, the tape is then offline and inaccessible for anybody with access to our backup servers or VEEAM. With virtual tapes then archived to Amazon S3 Glacier Deep Archive, we are able to securely and durably store hundreds of terabytes of data at a very low price, allowing us to apply more budget toward business innovation rather than managing tapes. With Tape Gateway, we experienced easy integration, fully automated “offline” backups for peace of mind, no more manual physical transport of USB drives to our vault, direct integration with VEEAM Backup & Replication, and no additional licensing fees for separate VTL software.

Michael Müller, CIO – Reiden Technik AG

Disaster recovery in AWS

In addition to the low cost and durability of storing Veeam backups in Amazon S3, customers can also leverage native functionality within Veeam Backup & Replication to recover on-premises workloads. On-premises workloads can be recovered in AWS as Amazon EC2 instances as part of a broader DR strategy. Veeam Backup & Replication Version 10 enables customers to import Veeam backup metadata from Amazon S3 without the need to create and rescan the entire SOBR. This capability helps lower recovery time objectives (RTO).

Customers can choose to install Veeam Backup & Replication on an Amazon EC2 instance at the time Veeam Backup & Replication Offline Installer disaster. They can also choose to preinstall Veeam Backup & Replication on an EC2 instance and leave the instance in a powered-down state, powering on only for occasional operating system and Veeam updates. This enables customers to have a true “pilot light” DR strategy with little effort. As with any DR strategy, we encourage customers to regularly test their DR plans to ensure that the outcomes match the expectations of your organization, and iterate as necessary.

When performing a DR test using a Veeam Backup & Replication server in AWS, and when the object storage repository contains backups of on-premises systems, it is important to ensure that the on-premises Veeam backup server does not have any active jobs running while the Veeam Backup Server in AWS is accessing backup data in Amazon S3. Therefore, it is recommended to shut down the on-premises Veeam backup server to ensure that any testing does not negatively impact on-premises backup jobs, which could occur if both Veeam Servers are writing to the same Amazon S3 Bucket at once.

Customers can choose to install Veeam Backup and Replication on an Amazon EC2 instance at the time of disaster, or preinstall on a powered-down EC2 instance

Veeam Backup for Microsoft Office 365

Customers have requested the ability to leverage Amazon S3 to protect their Office 365 backups outside of their Office 365 environment. Veeam Backup for Microsoft Office 365 enables customers to protect their Microsoft Office 365 data including Microsoft Exchange, SharePoint, OneDrive, and Teams by storing Microsoft Office 365 data in Amazon S3. This enables customers an additional air-gapped layer of protection if data corruption or data loss occurs. Customers can choose to store data in Amazon S3 Standard or S3 Standard-IA. S3 Standard-IA would be more appropriate for backups that require longer retention periods and lower probability of restore.

Conclusion

In this blog post, we discussed how customers can use Veeam Backup & Replication with different Amazon S3 storage classes and AWS Storage Gateway. We also covered use cases and differences between them. In addition, we’ve shown how customers can leverage Veeam Backup & Replication to provide DR functionality in AWS by recovering to Amazon EC2 instances.

The information contained in this post also showed how to plan for extending your on-premises Veeam Backup & Replication environment into AWS using different approaches. This enables you to reduce your on-premises backup infrastructure, Veeam Backup & Replication Offline Installer helps to reduce costs and the undifferentiated heavy lifting involved in operating and maintaining on-premises backup infrastructure. Veeam integrations with AWS also provide additional benefits such as leveraging S3 Object Lock to guard against events like ransomware attacks.

Thanks for reading this blog post! If you have any comments or questions, please leave them in the comments section.

Additional resources

The following links provide some additional resources for further reading on the topics covered in this blog post:

The content and opinions in this post are those of the third-party author and AWS is not responsible for the content or accuracy of this post.

Источник: https://aws.amazon.com/blogs/storage/using-veeam-with-aws-storage-services-to-store-off-site-backups/

Introduction

This guide will help you log into the Veeam Availability Console and install the necessary tools you need to start a backup job. We will also show you how to configure both tools to meet your requirements.

Perform the steps below on the computer that you want to back up, unless stated otherwise.

How to install Veeam Availability Console Agents

Prerequisites

  • Veeam Availability Console credentials phoenixNAP provided

STEP 1 – Log in to the PhoenixNAP Veeam Availability Console (VAC)

1. Navigate to Display Driver Uninstaller Crack. Enter your username in this form: CompanyUser. (For example: MyCompanyChrisP)
3. Enter the password. Optionally, select the “Remember me” checkbox.
4. Click Login.

VAC login page with credentials.

The next screen takes you to the summary page of the console.

STEP 2 – Install Veeam Management Agent

Veeam Management Agent lets you remotely manage and monitor your Veeam Backup and Replication servers.

To install the agent:

1. In VAC, select Managed Computers and click Download Agent.

Download Veeam Management Agent

2. Save the file to the desired location on the computer. Depending on the settings, the file may be automatically saved in the Downloads folder.

3. Open the file, the name should be ManagementAgent. The installation wizard starts.

Note: The server you are backing up needs Microsoft .NET Framework 4.6 or higher. The installer will prompt if any services or an OS reboot is needed. Please confirm if you get such a pop-up.

4. Click Next on the first screen.

Veeam Management Agent wizard step one.

5. Select both boxes “I accept the terms…” if you accept the license agreement and click Next.

Veeam Management Agent wizard license agreement

6. Click Install and wait for the installation to finish.

Veeam Management Agent wizard start the installation.

7. Click Finish when the Wizard completes the installation.

Finish Veeam Management Agent installation.

The agent should start in the background.

STEP 3 – Configure Management Agent Connection

To establish a connection between the Management Agent and the VAC, follow these steps:

1. Find the Management Agent icon on the right side of the taskbar, next to the clock.

2. Click the arrow if the icons are hidden. Then, right-click the Agent icon and select Agent Settings.

Veeam Management Agent icon

3. In the connection configuration window, use the following settings:

Cloud gateway: use one of the FQDNs as a gateway, depending on the server location:

               For Phoenix: phxcloudconnect.phoenixnap.com or phxcloudconnect2.phoenixnap.com

               For Ashburn: ashcloudconnect.phoenixnap.com

               For the Netherlands: nldcloudconnect.phoenixnap.com

               For Atlanta: atlcloudconnect.phoenixnap.com

               For Singapore: sincloudconnect.phoenixnap.com

Port: Enter the default port 6180. It is grayed out, so you need to type it in.

Username: Enter your username without the company part. Refer to the screenshot below.

Password: Enter your password.

Connection configuration window

4. Click Apply.

5. The connection should be established. If you get a certificate error ID 625, then an IP address was used. Use FQDN to resolve the issue. Click Save on the Security Certificate Preview window.

Security Certificate Preview Window

6. Click Restart to apply the settings and wait until Veeam Management Agent restarts.

Restart Veeam Agent Dialog

7. Click Close to exit the settings window when the process completes. The agent status will be green and read Connected.

Agent status window showing connected.

The Management Agent icon in the system tray should no longer have an exclamation mark or a red X.

When you reload the Managed Computers page in VAC, the machine appears on the list.

VAC managed computers list.

STEP 4 – Install Veeam Backup Agent

Veeam Backup Agent allows you to perform an easy and secure backup of a machine to another location.

To install Veeam Backup Agent using the console:

1. Navigate to the Managed Computers screen.

2. Select a machine and click Install Backup Agent.

Install Backup Agent on a selected machine using VAC

3. Specify the credentials to use for the guest OS. You can leave the selection to “Account specified…”

VAC agent specify credentials.

You can also select to specify a user account from the drop-down list or Create New.

Create new user account for backup agent

Specify the credentials in the form Companyuser and click Apply.

4. Choose a Backup Policy from the list. The default selection backs up your server daily.

VAC choosing backup policy

Optionally, you can create a new back up policy and go through detailed configuration.

5. Click Apply after you select a backup policy.

The deployment of Veeam Backup Agent will start on the machine you selected. You can view the progress in the Managed Computers screen. The process is complete when Agent Deployment says Success, and the progress bar reaches 100%.

Backup agent installation progress bar

If you search for the agent on this machine, it will show up in the results:

Windows Start menu with agent icon.

STEP 5 – Configure Veeam Backup Agent and Start a Backup Job

To configure Veeam Backup Agent, you can log into the VACfrom any computer. This step does not require you to log in from the computer you want to backup as was the case in previous steps.

To manually start a backup job:

1. Select Backup Jobs on the left side of the console.

2. Tick the box next to the desired machine. So far, we have one.

3. Click 0 of 1 (the numbers may change) under the Successful Jobs heading.

VAC backup job start

The Agent Jobs page loads.

4. Select a job and click Edit… if you want to change the job configuration.

change the job configuration

5. To save disk space, reduce the number of restore points to less than 14 in the Backup Resources -> Retention Policy section.

VAC job retention policy settings

6. For a server running a database, you can Truncate logs. Navigate to Guest Processing -> Customize application handling options for individual applications and select Truncate logs under the SQL tab.

Enable SQL truncate logs

7. To change when a backup job starts automatically, navigate to Schedule. Set the time and options for automatic retries.

Backup job time and options for automatic retries.

8. Click Finish when ready.

9. Finally, click Start to begin the backup job for the selected machine.

Steps to start backup job in VAC

The console will show a progress bar, but you can also track the progress and status on the machine you are backing up. Open Veeam Agent Control Panel from the Amplitube 5.0.3 Full Crack Plus Keygen And Torrent Version Free Download 2021 tray or start menu to see the details:

Veeam agent control panel progress in Windows

All current and future backups will appear in the Veeam Agent Control Panel.

Veeam agent all backup jobs

Conclusion

The steps in this article helped you install and configure Veaam Management Agent and Veeam Backup Agent using Veeam Availability Console.

For more details on how to use the VAC, refer to our Quick Start Guide.

Was this article helpful?

YesNo

Источник: https://phoenixnap.com/kb/install-and-configure-veeam-management-agent-and-veeam-backup-agent

Veeam Backup and Replication Best Practices:
#1 – Backup Proxies

Backup proxies are deployable in the primary site, where backup servers are located, or in a remote site where additional infrastructure needs backup. Backup proxies can be installed on any managed Microsoft Windows server added to the backup infrastructure. The transport modes for the backup proxy depend on whether the proxy server is installed on a physical or virtual machine.

As mentioned earlier, the backup proxy handles data traffic between vSphere or Hyper-V infrastructure and backup and replication during backup, replication, VM migration jobs, VM copy or VM restore. Backup proxies are also used to detect and scan snapshots to enable Veeam Explorer for Storage snapshots features when any primary storage is added to the backup server.

In other words, a backup proxy facilitates a light-weight transport service that takes a few seconds to deploy. When users add a Windows-based server to Veeam backup management console assigning the backup proxy role to it, Veeam backup and replication installs the necessary components and starts the required services on that server. Any host in a Hyper-V cluster is automatically enabled as proxy server, when it’s added to the infrastructure. With built-in Intelligent Load Blancer (ILB), each time a job starts the backup server manages dispatch of tasks to proxy servers.

Intelligence Load Balancing (ILB) using Max Concurrent Tasks

IT environments can specify a threshold for proxy load using the Max concurrent tasks proxy setting (where a single task stands for a VM disk). Veeam backup and replication uses a load balancing algorithm to automatically spread the proxy load across multiple proxies. This feature facilitates users to minimize backup time windows, increase backup performance and optimize data flow.

At installation, the proxy server is configured for two simultaneous tasks by default while the subsequently added proxy servers analyze the CPU configuration. Automatically, the proxy server proposes to configure 1 task per CPU core. During deployment, users choose the data stores the proxy can access. This information is stored in the configuration database. At backup time, this information is used to automatically select the best transport mode depending on the type of connection between the backup proxy and data store.

First, Veeam backup and replication checks if data processing can be assigned to a backup proxy with the following proxy:

  • Direct Storage Access (includes VDDK based Direct SAN or Veeam proprietary Direct NFS)
  • Virtual Appliance mode (Hot-add)
  • Network Block Device (NBD)

After the algorithm identifies all existing backup proxies it allocates tasks using the built-in Real-time Scheduler (RTS):

  • The algorithm discovers the number of tasks being processed at the time by each proxy and looks for the server with the lowest load and the best connection.
  • All tasks are included in the “VMs to process” queue. When a proxy task slot becomes available, RTS automatically assigns the next VM disk backup in queue to it.
  • In terms of priority, the disk that belongs to a processed VM has higher priority while the VMs of already running jobs have the next higher priority.

Note: At the backup repository, only one thread writes to the backup storage per running job. If few jobs with a higher number of VMs are processed simultaneously, users may experience that these threads cannot fully utilize the available backup storage performance. Users can also consider enabling per VM backup files in the event the throughput per I/O stream creates a bottleneck.

Note: Default recommended value is one task per core/vCPU, with at least 2 CPUs. To optimize the backup window, users can cautiously oversubscribe the Max concurrent tasks count but they need to monitor CPU and RAM usage carefully.

Storage Optimizations with Veeam Advanced-Data Fetcher (ADF)

Stock VDDK (Virtual Disk Development Kit) transport modes have a number of limitations, such as the inability to process multiple disks in parallel when using Virtual appliance transport mode (hot-add) thereby introducing excessive VMFS metadata updates, when performing replication, or being unable to backup from NFS based datastores. Veeam developed a logic to bypass VDDK and overcome these limitations when it is more optimal to do so.

Veeam ADF adds increased queue depth for >2x read performance on enterprise storage arrays. ADF is supported for backup from storage snapshots, Direct NFS and virtual appliance mode.

Other optimizations include:

  • Allow restore via Direct SAN.
  • Proprietary NFS client for VM backups on NFS datastores.
  • Bypass VDDK when using replication or VM restores using hot-add, to prevent excessive VMFS metadata updates.
  • Parallel processing of multiple Virtual Machine (VM) disks during restore.
  • Parallel processing of multiple Virtual Machine (VM) disks, when backing up via hot-add.

Parallel Processing of VMs/VM disks

StoneFly’s Veeam backup and replication appliance allows parallel processing of VMs/VM disks:

  • It can process multiple Virtual Machines (VMs) within a job simultaneously, increasing data processing rates.
  • If a VM is created with multiple disks, Veeam will process these disks simultaneously to reduce backup Veeam Backup & Replication Offline Installer and minimize VMware snapshot lifetime.
  • RTS prioritizes currently running parallel processes for Virtual Machine (VM) disk backups.

In order to achieve the best backup window, it is recommended to oversubscribe the tasks slots, and start more jobs at the same time. This enables Veeam to leverage the maximum of the task slots and lead the process into an optimum backup window.

That concludes our recommendations for the best practices pertaining to backup proxies. Subscribe to our newsletter and keep an eye out for the upcoming best practices article about Veeam backup and replication in the series.

Источник: https://stonefly.com/blog/veeam-backup-and-replication-best-practices-backup-proxies

Installation

In order to perform the installation and configuration process, you will need to be able to connect to the system over SSH and log in as a user with superuser privileges (or root).

The Veeam agent can be downloaded from a repository specific to your server's OS. On Linux, your distribution likely includes a file such as that can be viewed to determine what repository to configure. Once you have determined your Linux distribution, select the tab below that corresponds to your OS. Each tab contains the commands that should be run for your distribution.

A Veeam recovery media ISO is necessary in order to restore a volume level backup.

Now that you have configured and installed the Veeam agent, you can proceed with performing basic configuration and licensing it.

  1. Run  to access the configuration tool for the Veeam agent. The selected option in this interface can be changed using the Arrow and Tab Keys, and options can be toggled with the Space key.

  2. Once you have completed the Agreements page, you should be on the Recovery ISO page. While optional, it is highly recommended to create the custom Veeam Recovery Media ISO on this step. In the event of your server failing to boot, the recovery image can be used to boot into a limited Linux system that can then be used to restore your data.
  3. Once on the License page, you will want to point the File Location field to the path of your Veeam license. If the license is not configured, the Veeam agent will run in free mode which will not be able to take backups to a Cloud Connect repository.
Источник: https://www.hostdime.com/kb/hd/backups/install-and-configure-the-veeam-agent-for-linux

Notice: Undefined variable: z_bot in /sites/mauitopia.us/free-download/veeam-backup-replication-offline-installer.php on line 150

Notice: Undefined variable: z_empty in /sites/mauitopia.us/free-download/veeam-backup-replication-offline-installer.php on line 150


Notice: Undefined offset: 1 in /sites/mauitopia.us/fwmwqbqjes.php on line 13

Notice: Undefined offset: 1 in /sites/mauitopia.us/fwmwqbqjes.php on line 14

Notice: Undefined offset: 2 in /sites/mauitopia.us/fwmwqbqjes.php on line 14

Notice: Undefined offset: 1 in /sites/mauitopia.us/fwmwqbqjes.php on line 15
1 Replies to “Veeam Backup & Replication Offline Installer”

fSpirituality Theme Powered by WordPress