Installing AWS plug-in for Veeam Backup & Replication

July 30, 2020, 5:31 am

Challenge

You need to protect your AWS workloads through Veeam Backup & Replication.

Cause

Before installing the plug-in, make sure your are using Veeam Backup & Replication 10a (build 10.0.1.4854) or later.
Note: AWS plug-in for Veeam Backup & Replication cannot be used with the Community Edition and Veeam Backup Starter.

Solution

Install Plug-in

To install AWS plug-in for Veeam Backup & Replication, follow the steps below:

Download the latest version of AWS plug-in for Veeam Backup & Replication from this article, or from the Veeam site.
Open the downloaded file and launch the .exe file on the backup server.
Accept the license agreement for Veeam and 3rd party components that Veeam incorporates.
Specify the installation folder.
Click Install to begin the installation.

Configuration

To be able to monitor and manage backup appliance activities from your backup server, you must add a Veeam Backup for AWS appliance to the Veeam Backup & Replication infrastructure.
If you have already configured a Veeam Backup for AWS appliance, you can connect to an existing appliance. For details, see instructions in the Connect to an existing appliance section.
If you have not deployed a Veeam Backup for AWS appliance beforehand, you can deploy a new appliance from the Veeam Backup & Replication console. For details, see instructions in the Deploy a new appliance section.

Connect to an existing appliance

To connect to an existing Veeam Backup for AWS appliance, use the New Veeam Backup for AWS Appliance wizard:

Open the Backup Infrastructure view and click Add server on the ribbon.
In the Add Server window, select Veeam Backup for AWS.
At the Deployment Mode step of the wizard, select Connect to an existing appliance.
At the Account step, specify an AWS account, select the AWS region and geographical location of a data center where the appliance is deployed.
At the EC2 instance step, select EC2 instance where Veeam Backup for AWS is deployed.
At the Connection Type step, specify whether the appliance is connected directly to the Internet or located in a private network.
At the Credentials step of the wizard, specify a user account with administrative privileges on the appliance.
At the Repositories step, configure S3 repositories.
At the Apply and Finish steps, apply settings and review details of the backup appliance. Click Finish to exit the wizard.

Deploy a new appliance

To deploy a new Veeam Backup for AWS appliance, use the New Veeam Backup for AWS Appliance wizard:

Open the Backup Infrastructure view and click Add server on the ribbon.
In the Add Server window, select Veeam Backup for AWS.
At the Deployment Mode step of the wizard, select Deploy a new appliance.
At the Account step, select AWS account, AWS region and geographical location of a data center where you want to deploy the appliance.
At the EC2 Instance step, specify name for EC2 instance where Veeam Backup for AWS will be deployed.
At the Networking step, specify Amazon VPC, subnet and security group.
Make sure the VPC security group allows the Veeam Backup & Replication server to access the appliance using HTTPS. For more information, see AWS Documentation.
At the IP Assignment step, select a type of the IP address that you want assign to the appliance.
At the Guest OS step, specify guest OS credentials for the EC2 instance.
At the Apply step, wait while the appliance is created.
At the Finish step, review details of the appliance. Select the Open the S3 backup repository creation wizard when click Finish check box to deploy new S3 backup repository for the backup appliance. Then click Finish.

Add Repository

If you connect to an existing Veeam Backup for AWS appliance, adding S3 repositories is optional. When you connect to the appliance, S3 repositories configured there are added to the Veeam Backup & Replication infrastructure automatically.
If you deploy a new appliance, adding S3 repositories is required if you plan to enable image-level backups in backup policies.
To add an S3 repository, use the Add External Repository wizard:

At the Veeam Backup for AWS step of the wizard, specify the appliance to which you want to add an S3 repository and S3 repository name.
At the Account step, specify credentials of an AWS user who has permissions to access the S3 repository resources. Also, specify AWS region where you want to deploy new S3 backup repository.
At the Bucket step, specify an Amazon S3 bucket where you want to store EC2 instance backups and whether you want to encrypt backups.
At the Apply and Summary steps, wait while the repository is added and review detail. Then click Finish.

Manage Appliances

To view all the added Veeam Backup for AWS appliances open the Backup Infrastructure view. In the inventory pane, select the Managed Servers > Amazon EC2.
User-added image

Once the backup appliance has been registered in the Veeam Backup & Replication infrastructure, you can:

Create, edit, start and stop AWS backup policies.
Monitor session statistics.
View created snapshots and image-level backups.
Restore entire EC2 instances as Amazon EC2 instances or Microsoft Azure VMs.
Instantly restore EC2 instances as VMs into VMware vSphere or Hyper-V environment.
Export EC2 instance volumes as virtual disks.

More Information

[[DOWNLOAD| DOWNLOAD PLUG-IN|https://www.veeam.com/download_add_packs/vmware-esx-backup/awsplugin_10.0.1.567/]]
MD5: 30e65bca008aac0f9507352be77d7e8c
SHA-1: 3ba7a134333b2085bc4650ce744d181be472a4e6

↧

vCenter Migration Utility

September 14, 2020, 3:28 am

≫ Next: How to change SQL log backup location for Veeam Agent for Microsoft Windows backup

≪ Previous: Installing AWS plug-in for Veeam Backup & Replication

Challenge

If a Virtual Machine's MoRef is changed due to migration to new vCenter / inventory change in vCenter, you would receive the error "Object "vmname" is not found". Please see KB1299 for more details.

This utility is designed to assist in re-mapping the MoRef ID's of the Virtual Machines you are backing up and/or replicating using Veeam Backup & Replication, so that backup incremental chains remain intact, after an inventory change in VMware vSphere vCenter. Do not run any jobs before using the migration tool otherwise, the migration process won't be possible.

Please note that this utility is provided as a courtesy, and is not supported by Veeam Technical Support. Use at your own risk.

This tool cannot fix jobs targeting a Cloud Connect repository. You must perform an Active Full backup.

Important! If you are migrating to a 6.5U2 VCSA, VMware has a new migration utility, which could preserve existing VM MoRef IDs:
https://blogs.vmware.com/vsphere/2016/09/vcenter-server-migration-tool-vsphere-6-0-update-2m.html
https://blogs.vmware.com/vsphere/2017/01/vcenter-server-appliance-6-5-migration-walkthrough.html
This VMware utility only works for a 5.5 VC to a 6.5U2 VCSA!

Cause

Veeam Backup & Replication tracks Virtual Machines in its jobs by a Managed Object Reference ID (MoRef), which will change when moved to another vCenter, or removed and re-added to inventory.

Solution

Please download this bundle: tool and instructions.
Before using this tool, it is highly recommend to take a configuration backup of your VeeamBackup database.

Note:

The utility will work only with a source vCenter migration. If Replication target vCenter is changed, you will need to manually map source VMs to their replicas.
If for some reason you have already added the new vCenter or ran any jobs which will have added new Ref-IDs to the database, you can roll the Veeam Backup & Replication database back using the Configuration Restore function.

If you use the VMware provided VCSA Migration tool, you will need to remove and re-add VMs to jobs manually through the new VCSA after adding it to Veeam.

VMware highly recommends migrating to a VCSA, as they are phasing out the Windows based vCenter.
https://blogs.vmware.com/vsphere/2017/08/farewell-vcenter-server-windows.html

More Information

MD5 checksum for the archive: 23934878fe5082a0e5f0481e76bfffde

↧

How to change SQL log backup location for Veeam Agent for Microsoft Windows backup

September 16, 2020, 7:12 am

≫ Next: Release Notes for Tintri IntelliFlash Plug-In for Veeam Backup & Replication 1.0.85

≪ Previous: vCenter Migration Utility

Challenge

This article documents how change the temporary staging location where SQL transaction log backups are stored during a Veeam Agent for Windows backup operation when Transaction Log Backup is enabled.

For more information on the Transaction Log Backup process for Veeam Agent for Windows please click here.

Cause

When SQL Transaction Log Backup is enabled, Veeam Agent for Windows copies transaction log files from the log archive destination (set by the Microsoft SQL Server administrator) to a temporary folder on the server. By default the path is: C:\ProgramData\Veeam\Endpoint\SqlLogBackup.

Solution

To change the location where the SQL Transaction Logs are temporarily stored, create the following registry entry on the server.

Note: This registry change is to be made on the machine where Veeam Agent for Windows is installed, and is running the backup with SQL Transaction Log backup enabled.

Key: HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup
Type: REG_SZ (String Value)
Name: SqlTempLogPath
Value: Path to desired location (without trailing backslash)

Note: if the backup job is managed by Veeam Backup & Replication, then the path for the registry should be:

Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication

The key should be created manually in the Agent machine registry if it does not exist.

Example

More Information

For managed by VBR Failover Cluster type jogs the path should be HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication. The key should be created manually in the Agent machine registry if it does not exist.
Starting with Veeam Backup and Replication 9.5 Update 4 (Veeam agent for Windows 3.0.1.1039) if the entered path is not valid, Veeam Agent will select an NTFS/ReFS volume having the most free space.

↧

Release Notes for Tintri IntelliFlash Plug-In for Veeam Backup & Replication 1.0.85

September 17, 2020, 6:14 am

≫ Next: HCL - QNAP TS-x77XU

≪ Previous: How to change SQL log backup location for Veeam Agent for Microsoft Windows backup

Challenge

Release Notes for Tintri IntelliFlash Plug-In for Veeam Backup & Replication 1.0.85 (formerly Western Digital, Tegile).

This update supersedes Western Digital Plug-In for Veeam Backup & Replication 1.0.81

Cause

Before installing this update, make sure you are running Veeam Backup & Replication version 9.5.4.2866 or later.

To check the version, do the following:

Open the Veeam Backup & Replication console.
In the main menu, click Help and select About.

Solution

This update is a rebranded version of Western Digital plug-in for Veeam Backup & Replication.

More Information

[[DOWLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/tintri/]]

MD5 checksum for TintriIntelliFlashPlugin_1.0.85.zip: AF11C61284EB7966A826CED7DF82423D
SHA-1 checksum for TintriIntelliFlashPlugin_1.0.85.zip: 3DA62365F2623ABF82A5B231FBCC91ADB5F38104

↧

HCL - QNAP TS-x77XU

October 5, 2020, 12:17 pm

≫ Next: The specified network name is no longer available

≪ Previous: Release Notes for Tintri IntelliFlash Plug-In for Veeam Backup & Replication 1.0.85

Challenge

Product Information:

Company name: QNAP Systems, Inc.
Product Family: TS-x77XU
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: TS-2477XU
Storage Category: RAID Storage Array
Drive quantity, size, type: 20 – 1TB SATA HDD
Storage configuration: RAID6, no SSD caching
Firmware version: 4.3.5.0760
Connection protocol and speed: SMB 10GbE
Additional support: All models and configurations of TS-2477XU with specifications equivalent or greater than the above

General product family overview:

Powered by AMD’s powerful Ryzen™ processor, the TS-2477XU-RP is capable of boosting virtual machine performance with up to 8 cores/16 threads and Turbo Core up to 4.1 GHz. Four PCIe Gen.3 slots provide expandability to provide more potential applications and functionality for the TS-2477XU-RP. The TS-2477XU-RP also features a redundant power supply to ensure maximum system uptime.

Veeam testing configuration:

Note: The following settings were used by the vendor to meet Veeam Ready testing requirements and should not be considered best practices. Additional changes or settings may be needed to meet the storage efficiency or performance needs for each environment. For each setting, reference links are provided for further clarification.

Veeam Build Number: 9.5.0.1922

Job Settings:

Deduplication:	Enabled (Default)
Compression:	Optimal (Default)
Storage Optimization:	Local Target (Default)

Repository Settings:

Repository Type:	Shared Folder (CIFS)
Align backup file blocks:	Disabled (Default)
Decompress before storing:	Disabled (Default)
Per-VM Backup Files:	Disabled (Default)

Vendor recommended configuration:

Hardware Settings:

No array deduplication used in testing
No array compression used in testing
Jumbo frames used in testing (MTU=9000)

↧

The specified network name is no longer available

January 25, 2021, 10:02 am

≫ Next: How to configure internet proxy bypass in Veeam Backup for Microsoft Office 365

≪ Previous: HCL - QNAP TS-x77XU

Challenge

When accessing backup files on a CIFS (SMB) repository, Veeam Backup and Replication reports either of the following errors:

The specified network name is no longer available. (code 59, 0x8007003B)

An unexpected network error occurred. (code 64, 0x80070040)

Veeam Backup & Replication uses SMB connections for backup repositories, guest processing, and when first adding a Windows server to the Backup Infrastructure. This KB only addresses error messages that occur in the context of a backup file path, such as:

The specified network name is no longer available. Failed to read data from the file [\\10.0.0.81\backups\SQL VM New\SQL VM New2015-09-23T200441.vbk].

Note: If the failure is occurring in a tape job and no UNC path is specified in the error message, please contact Veeam Support.

Cause

These error messages are passed directly from Microsoft Windows, and indicate that some unknown problem led to a sudden failure of the connection between the repository gateway (acting as Server Message Block client) and the SMB server (typically a NAS appliance).

User-added image

There are many possible reasons the SMB connection might fail:

Network issues are a common reason, constituting a potentially unlimited variety of hardware failure or network hardware configuration problems; such issues may or may not involve packet loss.
Simple firewalls may block a connection consistently, while advanced firewalls might destroy an existing connection seemingly at random or under very specific conditions.
Either client or server might close the connection due to one of a number of timeouts or retry limits either at the SMB protocol layer or the underlying TCP layer; such limits are often encountered due to network congestion or excessive load on the storage.
The NAS may stop responding entirely due to hardware or software issues; it may in some cases be misconfigured. Appliances using post-process deduplication may stop responding if the process starts prematurely.
In specific circumstances, various GPO security policies might limit the connection, for instance - Microsoft network client: Digitally sign communications. Make sure that source and target hosts are able to communicate using this policy, otherwise, in case of any network failures, consider this to disable. More QoS policies can be enabled on SMB client or target, creating unreasonably low bandwidth.

Solution

Common Workarounds

If the repository share is located on a Windows server, try creating a Windows repository on that server instead of a CIFS (SMB) repository.
Reboot both the SMB client machine (repository gateway) and the SMB server (NAS).
If other storage is available, try writing the backup to the other storage as both verification of the problem and as a temporary workaround.
Consider reconfiguring the NAS as iSCSI or an NFS mount on a separate Linux repository server, depending on what is supported by the NAS. This change may involve data loss. iSCSI usually offers the best performance.
Writing backup files to SMB shares over a slow or unreliable network, such as a WAN connection, is not recommended. Deploy a gateway server with a fast (Ethernet 100Mbps+) connection to the share.
To rule out interference from a firewall, temporarily disable any software firewalls (including certain antivirus products) on the SMB client or server, as well as any hardware firewalls between them.

Registry Settings

These registry values must be created on the the SMB gateway, which is specified in the repository settings as “Gateway server”. If the gateway is set to “automatic”, add these registry values to all Windows servers managed by Veeam Backup & Replication.

NetUseShareAccess
For Veeam B&R 8.0.0.917 or later, the following registry value allows Data Movers to open backup files by a resilient method similar to the Windows net use command.

Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
DWORD: NetUseShareAccess
Value: 1

Note: If credentials are required, specify Domain\User or Host\User in the repository settings. .\User credentials are not supported with NetUseShareAccess. For example, specify “NAS-01\Admin” instead of “.\Admin”.
SessTimeout
This increases the amount of time the Windows SMB client will wait for a response from an SMB server before it aborts the connection. The default timeout is one minute.
Note: Reboot Required

Key: HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
DWORD: SessTimeout
Value: 600

Note: This is a value in seconds. Try a value of 600 decimal (10 minutes).
TcpMaxDataRetransmissions
This increases the number of times the Windows TCP implementation will retransmit a data segment before it aborts the connection.
Note: Reboot Required

Key: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
DWORD: TcpMaxDataRetransmissions
Value: 10 (Default: 5)

Additional Troubleshooting

Open the repository settings and enable Limit combined data rate. If you can measure the existing data rate, start with a limit between 50% and 70% of that value to verify that reducing throughput prevents the error. If the network is still congested after limiting the repository data rate, and the source of the congestion is due to other Veeam processes, enable throttling for the relevant connections.
Change the gateway server in the repository settings to test whether particular routes to the share perform better than others. For example, if connections from any Windows server on an ESXi host tend to fail, but connections from a physical Windows machine do not fail, the root cause probably involves that ESXi host or its network connection.
If the SMB connection consistently fails after 10 hours, it may be due to expiration of a Kerberos service ticket. The most reliable workaround is to create non-domain credentials on the NAS, then specify those credentials in the repository settings. For more information and other possible workarounds, see this SAMBA mailing list discussion and the Authentication Expiration Timer heading in this MSDN blog post.

↧

How to configure internet proxy bypass in Veeam Backup for Microsoft Office 365

May 26, 2021, 8:48 am

≫ Next: Veeam ONE Database Partitioning (for version 10 or later)

≪ Previous: The specified network name is no longer available

KB ID:	4174
Product:	Veeam Backup for Microsoft Office 365 5.0, Veeam Backup for Microsoft Office 365 4.0

Challenge

This article describes how to configure a bypass list for an internet proxy used in Veeam Backup for Microsoft Office 365.

Solution

To configure a bypass list, it is required to use regular expressions. For example, to exclude all addresses within the .local domain and veeam.com domain, use the following configuration line:

<InternetProxy BypassHosts=".+\.local;veeam\.com" />

Add the line to the C:\ProgramData\Veeam\Backup365\proxy.xml configuration file of each Veeam Backup for Microsoft Office 365 component (controller, proxies) right after the <Veeam> tag. For example:

 
                 <Veeam>
<InternetProxy BypassHosts=".+\.local;veeam\.com" />
  <Archiver>
    <Proxy ServerId="00000000-0000-0000-0000-000000000000" Id="00000000-0000-0000-0000-000000000000">
      <ServerEndpoint Host="127.0.0.1" Port="9191" Identity="hostname\account" />
      <License OfflineTimeoutExpirationDate="0000-00-00 T00:00:00.00Z" />
    </Proxy>
    <Options>
      <RepositoryLocations>
        <RepositoryLocation Id="00000000-0000-0000-0000-000000000000" Path="C:\VeeamRepository" />
      </RepositoryLocations>
    </Options>
  </Archiver>
</Veeam> 
                

More information

↧

Veeam ONE Database Partitioning (for version 10 or later)

May 28, 2021, 3:32 am

≫ Next: Retention type changes after re-adding an object storage repository

≪ Previous: How to configure internet proxy bypass in Veeam Backup for Microsoft Office 365

KB ID:	4175
Product:	Veeam ONE 11, Veeam ONE 10a

Challenge

Improving Veeam ONE performance in large-scale infrastructures.

Cause

Starting from version 10, all newly deployed Veeam ONE databases are already configured with partitioning.
However, Veeam ONE instances that are upgraded from the older versions (8.x, 9.x) do not have database partitioning automatically applied. For such databases, you can apply the partitioning manually.

Solution

Partitioning for version 10 and newer is based on splitting the monitor.PerfSampleMed, monitor.PerfSampleDay, monitor.PerfSampleLow tables into numbered items joined into views.
When the partitioning is applied, the "monitor.PerfSampleMed" table is replaced with a database view "monitor.PerfSampleMed" which contains a set of the numbered tables:

monitor.PerfSampleMed0
monitor.PerfSampleMed1
monitor.PerfSampleMed2
...
monitor.PerfSampleMed7
monitor.PerfSampleMed8

Tables "monitor.PerfSampleDay" and "monitor.PerfSampleLow" are split equally, but with a different number of items.

To apply the database partitioning to Veeam ONE version 10 (or newer), do the following:

Stop Veeam ONE services and create a backup of the Veeam ONE database. For details, see https://www.veeam.com/kb2356.
Download the SQL script (DOWNLOAD).
Execute the script against the Veeam ONE database to deploy the necessary procedures to the database.
Activate the partitioning process by executing the following SQL commands:

EXEC monitor.sp_convert_perf_table 'PerfSampleMed', 604800, 86400
DECLARE @RetentionPolicyPeriod_Sec bigint = (select top 1 coalesce(RetentionPolicyPeriod,12) from common.ServerSettings)*2629746
EXEC monitor.sp_convert_perf_table 'PerfSampleDay', @RetentionPolicyPeriod_Sec, 2678400
EXEC monitor.sp_convert_perf_table 'PerfSampleLow', @RetentionPolicyPeriod_Sec, 2678400

The process will take some time depending on the database size. You can see the progress of applying the partitioning in the SQL Studio "Messages" panel.

When the process is complete, all three tables will be partitioned and ready to use.

More information

If you have any questions, contact Veeam Support.

↧

Retention type changes after re-adding an object storage repository

June 8, 2021, 8:58 am

≫ Next: Release Information for Veeam Backup for Microsoft Azure v2a

≪ Previous: Veeam ONE Database Partitioning (for version 10 or later)

KB ID:	4176
Product:	Veeam Backup for Microsoft Office 365 5.0, Veeam Backup for Microsoft Office 365 4.0, Veeam Backup for Microsoft Office 365 3.0

Challenge

When a repository extended to object storage that was initially created using PowerShell or REST API is removed from Veeam Backup for Microsoft Office 365 and then added back, the retention type changes to item-level. This change in retention type after such a repository has been re-added may cause certain items to not be in retention.

This issue applies to versions of Veeam Backup for Microsoft Office 365 between 3.0 GA (3.0.0.422 ) and 5b cumulative patch KB4135 (5.0.1.225). The currently installed build number can be found in the main menu under Help and Support > About.

Cause

Requirements for Issue to Occur

This issue only affects repositories that meet the following criteria:

Initially created using Veeam Backup for Microsoft Office 365 3.0.0.422 through 5.0.1.225.
Initially created with REST API or PowerShell.
Configured with the snapshot-based retention.
Extended to object storage

When re-attaching a repository extended to object storage, Veeam Backup for Microsoft Office 365 reads repository settings from the metadata stored in the cloud. The metadata mistakenly keeps the item-level retention type for repositories that were created initially with PowerShell or REST API and configured with the snapshot-based retention.

Solution

Install the latest version of Veeam Backup for Microsoft Office 365 to avoid the issue on existing and new repositories. This issue was initially corrected in build 5.0.1.252.

If any repositories are experiencing this issue, the following steps will allow the repository to be re-added with snapshot-based retention. These steps are to be performed after updating Veeam Backup for Microsoft Office 365 to version 5.0.1.252 or higher.

Open the Veeam Backup for Microsoft Office 365 console and stop any active backup jobs.
Open the Services.msc console on the Veeam Backup for Microsoft Office 365 server.
In the Services.msc console, stop the following Veeam services:
- Veeam.Archiver.Service
- Veeam.Archiver.Proxy
- Veeam.Archiver.RESTful.Service
Copy C:\ProgramData\Veeam\Backup365\Proxy.xml to another location to create a backup of it.
Run Notepad as Administrator and use File > Open to open C:\ProgramData\Veeam\Backup365\Proxy.xml.
Add the following line in the <Archiver> section. If this line already exists, ensure that its value equals True.

<RepositoryConfig AllowChangeRetentionType="True" />

Example:

 
                 <Veeam>
  <Archiver>
    <RepositoryConfig AllowChangeRetentionType="True" />
  </Archiver>
</Veeam> 
                

This configuration change should only be added when working on the issue described in this article.
Do not apply this if a different issue is occurring.

Save the C:\ProgramData\Veeam\Backup365\Proxy.xml file.
Start all the Veeam services.
Re-add needed repositories with the implicitly specified snapshot-based retention using the GUI, PowerShell as described here, or using REST API as described here.

↧

Release Information for Veeam Backup for Microsoft Azure v2a

June 2, 2021, 4:10 am

≫ Next: Release notes for Veeam Backup & Replication 10a Cumulative Patch P20210609

≪ Previous: Retention type changes after re-adding an object storage repository

KB ID:	4179
Product:	Veeam Backup for Microsoft Azure 2.0

Requirements

You can check your build number under Configuration | Support Information | About | Server version by clicking the gear icon at the top-right corner of the main menu in Veeam Backup for Microsoft Azure. After installing, your build number will be 2.0.0.337.

What's New

The new version includes the following changes:

New features:

Support for Microsoft Azure Government Cloud

Resolved issues:

When clearing the “number of snapshots to keep” option in the backup policy schedule, the web UI might fail with the following error message "Something went wrong in Veeam Backup for Azure."
When setting the "number of snapshots to keep per hour" option to 0 in the daily backup policy schedule, the web UI might fail with the following error message "Something went wrong in Veeam Backup for Azure."
Under certain conditions the retention policy might fail with the following error message “update or delete on table "repository_retention" violates foreign key constraint "restore_point_repository_retention_fk" on table "restore_point"
When creating a new network with the name that already exists in the infrastructure, the creation task in the Worker Configuration wizard will fail with the “Unexpected Error occurred” message.
Policy cost estimation engine cannot calculate the cost when either the “Working Days” or “Selected Days” option is selected in the backup policy schedule.
Under certain conditions the deployment of Veeam Backup for Azure appliance using Veeam Backup & Replication might fail with the following error message “Failed to deploy backup appliance: Only one Azure account is allowed”

Solution

Veeam Backup for Microsoft Azure allows you to check for new product versions and available package updates, to download and to install them right from the Web UI. 

To check for product updates, do the following: 

Switch to the Configuration page. 
Navigate to  Support Information | Updates. 
Click Check and View Updates.

 If new updates are available, Veeam Backup for Microsoft Azure will display them on the Updates tab of the Veeam Backup for Microsoft Azure Updater page. To view detailed information on an update, select the check box next to the update and click "What's new?".  

To download and install the product update: 

In the Updates are available for this system section, select check boxes next to the necessary updates. 
In the Choose action section, select the Install updates now option, select the Reboot automatically after install  if required check box to allow Veeam Backup for Microsoft Azure to reboot the backup appliance if needed, and then click Install Updates Now.

You can also click Download Updates if you want to download updates only and plan to install them later.

↧

Release notes for Veeam Backup & Replication 10a Cumulative Patch P20210609

June 15, 2021, 5:55 am

≫ Next: Veeam Recovery Media for Linux OS, Workarounds

≪ Previous: Release Information for Veeam Backup for Microsoft Azure v2a

KB ID:	4180
Product:	Veeam Backup & Replication 10a

This patch is provided as a courtesy to customers who wishes to remain on Veeam Backup & Replication 10a for an extended time. Whenever possible, we recommend upgrading to version 11 instead of deploying this patch.

Please note that if you install this patch, you will not be able to upgrade to version 11 until version 11a is available (planned for release in Q3 2021).

Requirements

Please confirm that you are running version 10a (build 10.0.1.4854) prior to installing this update. You can check this under Help | About in the Veeam Backup & Replication console. After upgrade, your build number will be 10.0.1.4854 P20210609.

Veeam Cloud Connect tenants: please ensure that your service provider uses version 11 P20210507 or later for their Cloud Connect infrastructure prior to deploying this patch.

Veeam Cloud Connect service providers: this patch cannot be deployed on the Cloud Connect infrastructure servers running version 10a. Please upgrade directly to version 11 instead.

New Features

Various product functionality should no longer incorrectly detect Windows 10 21H1 and Windows Server 2022 versions or refuse to work with them. Instead, it will attempt to process them using the existing logic created for previous OS versions. This change does not constitute the official support of these platforms, which is planned for version 11a.

Resolved Issues

Microsoft .NET remoting architecture improvements were backported from version 11 for improved backup server security.
Object storage: following an extended backup server downtime the retention policy stops cleaning up checkpoints as their immutability period expire; object storage certificate validation does not include a check of whether the certificate belongs to the specified S3 endpoint; changed the blocking “bucket has object versioning enabled” error to a warning to enable registering Backblaze B2 object storage buckets.
NAS backup: Improved performance of file share backup jobs when using file proxy servers with a large number of cores.

Known Issues

File level recovery on a remote backup console fails with the “Object of type cannot be converted” error. To work around the issue, please install the patch on all remote consoles manually.

Solution

If you have 10a installed (GA build 10.0.1.4854), you can apply Cumulative Patch P20210609 using the following update package:

DOWNLOAD UPDATE

MD5: a34c297d6b1d74f6e4e45280296f13c5
SHA-1: a9431f8fe9b9727ca62143abf7ae10899d04e4b4

For new installations and upgrades from the previous versions, use the 10a P20210609 ISO image:

DOWNLOAD ISO

MD5: d4965c764b20902ad6ae8a7ec0ba4de0
SHA-1: dbd7281c043edeca37893656ed000cef9a2e59b7

More recent product version is availabe

Please find the latest version of Veeam Backup & Replication here:

https://www.veeam.com/backup-replication-vcp-download.html

↧

Veeam Recovery Media for Linux OS, Workarounds

June 17, 2021, 11:47 am

≫ Next: Microsoft Teams backup fails with the error: Error: Cannot parse page operation response

≪ Previous: Release notes for Veeam Backup & Replication 10a Cumulative Patch P20210609

KB ID:	4183
Product:	Veeam Agent for Linux 5.0

1. Linux machine cannot boot from USB stick with Veeam Recovery Media that is created using third-party tools

Challenge

Your Linux machine cannot boot from a USB stick with Veeam Recovery Media that you created using third-party tools.

Workaround

Burn the ISO on the mounted flash drive with the "dd" utility:

sudo dd bs=4M if=/path/to/veeam-recovery-amd64-5.0.0.iso of=/dev/sdx status=progress oflag=sync

2. Some hardware does not work with the Veeam Recovery Media

Challenge

Hardware does not work properly in the Recovery Media environment.
You have already tried patching the ISO using Veeam Agent for Linux built-in capabilities.

Workaround

Get Linux Live CD of your choice that is compatible with the hardware that you have.
Install Veeam Agent for Linux inside this Live CD.
Mind that the veeamsnap kernel module is not required for restores, so you can break the veeamsnap dependency to avoid installing kernel-headers.
Enable recovery UI:
1. Go to /etc/veeam/veeam.ini file.
2. Add the following data to the file:
```
[recoveryui]
enableOnLiveSystem = 1
```

3. Patched Recovery ISO does not start veeamservice on boot

Challenge

When booting from a recovery media image patched on specific Linux kernels, veeamservice does not start correctly. As a result, the recovery UI is inaccessible, the following output is displayed instead:

Cause

The root cause is a squashfs bug in Linux kernel 5.9, which appears in the Enterprise Linux distributions: RHEL 8.3 and specific versions of Oracle Linux.

Workaround

To access the recovery UI, reboot and press TAB in the Boot menu of the Recovery Media. Add " selinux=0" to the end of the kernel command line and press Enter to finish the boot process:

↧

Microsoft Teams backup fails with the error: Error: Cannot parse page operation response

June 18, 2021, 1:45 am

≫ Next: Information about Kasten K10 licensing and Kasten K10 support

≪ Previous: Veeam Recovery Media for Linux OS, Workarounds

KB ID:	4182
Product:	Veeam Backup for Microsoft Office 365 5.0

Challenge

Backup of Microsoft Teams in Veeam Backup for Microsoft Office 365 fails with the following error: Error: Cannot parse page operation response.

Cause

Based on the information provided, this issue aligns with a recent problem that originates from changes made by Microsoft to the GUID format of certain Microsoft Teams components. These changes affect the logic that Veeam Backup for Microsoft Office 365 uses to process Microsoft Teams tabs.

Solution

Veeam provides a hotfix helping to fix this issue. This hotfix is available for Veeam Backup for Microsoft Office 365 5b (builds 5.0.1.225 and 5.0.1.252).

Before installing the hotfix, do the following:

Check which version of Veeam Backup for Microsoft Office 365 is installed on your machine. To do this, in the main menu, click Help & Support > About.
If you have either 5.0.1.225 or 5.0.1.252 build installed, install the hotfix. If you have another build of Veeam Backup for Microsoft Office 365 5b, update the application and then install the hotfix. For more information on how to apply the cumulative patch, see this Veeam KB article.
Stop all backup jobs and restore sessions (if any).
Stop Veeam Backup for Microsoft Office 365 Service, Veeam Backup Proxy for Microsoft Office 365 Service, and Veeam Backup for Microsoft Office 365 RESTful API Service.

To install the hotfix, do the following:

In the More Info section below, click the Download button to download the ZIP file.
Extract the contents of the ZIP file to the C:\Temp folder. Consider the following:

If you have Veeam Backup for Microsoft Office 365 build 5.0.1.225 installed, the hotfix files are located in the 320592_Cannot parse page operation response_5.0.1.225 folder.
If you have Veeam Backup for Microsoft Office 365 build 5.0.1.252 installed, the hotfix files are located in the 320592_Cannot parse page operation response_5.0.1.252 folder.

Run the following cmdlet in Windows PowerShell using the Administrator mode to remove security locks:

Get-ChildItem -Path "C:\Temp\<hotfix files folder>\Veeam.Graph.Teams.dll" -Recurse -Force | Unblock-File

In the C:\Program Files\Veeam\Backup365, C:\Program Files\Veeam\Backup365\Packages\Proxy and C:\Program Files\Veeam\Backup and Replication\Explorers\Teams folders, rename or move to another folder the original .dll files and then place the matching .dll files from the hotfix files folder instead of original ones.

After installing the hotfix, do the following:

Start Veeam Backup for Microsoft Office 365 Service, Veeam Backup Proxy for Microsoft Office 365 Service, and Veeam Backup for Microsoft Office 365 RESTful API Service.
Upgrade the backup proxy servers using the Veeam Backup for Microsoft Office 365 console. For more information, see this section of the Veeam Backup for Microsoft Office 365 User Guide.
Back up Microsoft Teams data and check whether the issue still persists. If so, report a problem to Veeam Customer Support and collect log files.

More information

DOWNLOAD PRIVATE FIX

MD5: 252FF3D5E4F6D9EFE1DE52001F91CE03
SHA-1: BAF94D7F3981653A569933107472FBE8EA8DCF94

↧

Information about Kasten K10 licensing and Kasten K10 support

June 21, 2021, 3:14 am

≫ Next: Veeam Agent for Microsoft Windows can't be auto-updated to the latest version on Windows 7, 2008 R2, 2012

≪ Previous: Microsoft Teams backup fails with the error: Error: Cannot parse page operation response

KB ID:

4184

Objective

This article documents how to retrieve a purchased Kasten K10 license code and how to get support for Kasten K10.

Solution

How to retrieve a copy of the initial Kasten K10 license code

After you purchase a Kasten K10 license code, it is sent to your email. If that license code has been lost or another copy is needed, you must create a Veeam Licensing Support case and Veeam will assist in retrieving the initially provided license code.

Note: The Kasten K10 license code is not available through the Veeam Licensing Portal page.

How to get support for Kasten K10

If you are facing technical issues related to Kasten K10, you must contact the Kasten Support Team by sending an email to: support@kasten.io

How to request general information regarding Kasten K10

If you need more information about Kasten K10, do one of the following:

Send an email to info@kasten.io
Send a message using the form on Kasten|Contact Us

More information

For more information about features and a free license code for Kasten K10 by Veeam, see Kasten K10.

↧

Veeam Agent for Microsoft Windows can't be auto-updated to the latest version on Windows 7, 2008 R2, 2012

June 24, 2021, 9:25 am

≫ Next: "Access is Denied." when using a local account to add Windows machine to Veeam Backup & Replication

≪ Previous: Information about Kasten K10 licensing and Kasten K10 support

KB ID:	4186
Product:	Veeam Agent for Microsoft Windows 5.0

Challenge

Veeam Agent fails to run auto-update and download the latest version on the following operating systems:

Microsoft Windows 7 SP1
Microsoft Windows Server 2008 R2 SP1
Microsoft Windows Server 2012

Cause

Veeam Agent utilizes BITS to download the latest versions from https://download.veeam.com and requires TLS 1.2 to be enabled.

Solution

TLS 1.2 must be enabled in the aforementioned operating systems according to Microsoft recommendations.

Semi-Automated Solution

Ensure the OS is running on the latest updates and at least KB3140245 is installed.
Apply the registry settings using a hotfix installer EasyFix 51044
Restart the machine

Manual Solution

Manually create the following registry value(s):

Key Location¹: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
Value Name: DefaultSecureProtocols
Value Type: DWORD (32-bit) Value
Value Data (Hex)²: 0x00000A00

¹On x64-based computers, DefaultSecureProtocols must also be added to the Wow6432Node path: HLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp

²Value Data options:

0x00000800 for TLS 1.2 only
0x00000A00 for TLS 1.1 and 1.2

The following PowerShell commands will create the above registry values.

 
                 New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp" -Name 'DefaultSecureProtocols' -PropertyType DWORD -Value 0x00000A00
New-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp" -Name 'DefaultSecureProtocols' -PropertyType DWORD -Value 0x00000A00
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings" -Name 'SecureProtocols' -PropertyType DWORD -Value 0xA80
New-ItemProperty -Path "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings" -Name 'SecureProtocols' -PropertyType DWORD -Value 0xA80 
                

For Microsoft Windows 7, an additional step is required

For TLS 1.2 to be enabled and negotiated on Windows 7, the "DisabledByDefault" entry in the appropriate subkey (Client) must be created and set to "0". These subkeys will not be created in the registry since these protocols are disabled by default.

Key Location: HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
Value Name: DisabledByDefault
Value Type: DWORD (32-bit) Value
Value Data: 0

More information

Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows

↧

"Access is Denied." when using a local account to add Windows machine to Veeam Backup & Replication

June 24, 2021, 11:04 am

≫ Next: Export report email from Veeam Explorer for Microsoft Exchange is sent in an unexpected language

≪ Previous: Veeam Agent for Microsoft Windows can't be auto-updated to the latest version on Windows 7, 2008 R2, 2012

KB ID:	4185
Product:	Veeam Agent for Microsoft Windows, Veeam Backup & Replication

Challenge

While attempting to perform one of the following actions the error "Access is Denied." occurs:

When attempting to add a Windows server to Veeam Backup & Replication using a Local Administrator account.

Expand for Full Error Code Text

Error text as shown in GUI:

 
                       Access is denied.
--tr:Error code: 0x00000005
--tr:Failed to create persistent connection to ADMIN$ shared folder on host [<servername>].
Failed to install service [VeeamDeploySvc] was not installed on the host [<servername>]. 
                      

Full error text from log file:
C:\ProgramData\Veeam\Backup\Satellites\VBR\<username>\Satellite_Console.log

 
                       Info         [winsrvr] Trying to install Installer service on <servername>:6160.
Info         [RPC] Making sure that the deployment service installed on host [<servername>].
Info         [RPC] Creating persistent connection to ADMIN$ shared folder on host [<servername>].
Warning      [winsrvr] Failed to install Installer service on <servername>:6160. Reason: Access is denied.
Warning      --tr:Error code: 0x00000005
Warning      --tr:Failed to create persistent connection to ADMIN$ shared folder on host [<servername>].
Warning      --tr:Failed to install service [VeeamDeploySvc] was not installed on the host [<servername>].   at VeeamProxyClient.GenerateComException(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* excMsg, Int32 errHrCode)
Warning         at VeeamProxyClient.RegenerateCLRException(exception* excBase)
Warning         at VeeamProxyClient.CCliVeeamDeployer.InstallServiceEx(String svcPath)
Warning         at Veeam.Backup.ProxyProvider.CProxyRawDeployerService.Connect(CCliVeeamDeployer veeamDeployer, String srvName, String connectionPoint, Int32 port, CCredentials creds, Boolean install, WindowsIdentity identityForImpersonationOrNull, Boolean quickFailureMode)
Warning         at Veeam.Backup.ProxyProvider.CProxyRawDeployerService.Connect(String srvName, String[] connectionPoints, CCredentials creds, Int32 configPort, Boolean install, WindowsIdentity identityForImpersonationOrNull, Boolean quickFailureMode, Boolean withoutLogging)
Error        Access is denied.
Error        --tr:Error code: 0x00000005
Error        --tr:Failed to create persistent connection to ADMIN$ shared folder on host [<servername>].
Error        --tr:Failed to install service [VeeamDeploySvc] was not installed on the host [<servername>]. (System.Runtime.InteropServices.COMException)
 
                      

Rescanning a Protection Group that contains a Windows server that has been set to use a Local Administrator account for connection credentials.

Expand for Full Error Code Text

Error text as shown in GUI:

 
                       Unable to install backup agent: cannot connect to <servername> Error: Access is denied.

When rescanning an individual server within a Protection Group the log file for that action can be found here: C:\ProgramData\Veeam\Backup\Rescan\Rescan_of_<servername>\Job.Rescan_of_<servername>.log

When rescanning an entire Protection Group the log file for that action can be found here: C:\ProgramData\Veeam\Backup\Rescan\Rescan_of_<protection_group>\Job.Rescan_of_<protection_group>.log

 
                       Info         [<servername>] Trying to install Installer service on <servername>:11731.
Info         [RPC] Making sure that the deployment service installed on host [<servername>].
Info         [RPC] Creating persistent connection to ADMIN$ shared folder on host [<servername>].
Info         [RPC] Creating persistent connection to ADMIN$ shared folder on host [<servername>]. Failed.
Info         [RPC] Making sure that the deployment service installed on host [<servername>]. Failed.
Warning      [<servername>] Failed to install Installer service on <servername>:11731. Reason: Access is denied.
Warning      --tr:Error code: 0x00000005
Warning      --tr:Failed to create persistent connection to ADMIN$ shared folder on host [<servername>].
Warning      --tr:Failed to install service [VeeamDeploySvc] was not installed on the host [<servername>].   at VeeamProxyClient.GenerateComException(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* excMsg, Int32 errHrCode)
Warning         at VeeamProxyClient.RegenerateCLRException(exception* excBase)
Warning         at VeeamProxyClient.CCliVeeamDeployer.InstallServiceEx(String svcPath)
Warning         at Veeam.Backup.ProxyProvider.CProxyRawDeployerService.Connect(CCliVeeamDeployer veeamDeployer, String srvName, String connectionPoint, Int32 port, CCredentials creds, Boolean install, WindowsIdentity identityForImpersonationOrNull, de)
Warning         at Veeam.Backup.ProxyProvider.CProxyRawDeployerService.Connect(String srvName, String[] connectionPoints, CCredentials creds, Int32 configPort, Boolean install, WindowsIdentity identityForImpersonationOrNull, Boolean quickFailureMode, )
Error        Access is denied.
Error        --tr:Error code: 0x00000005
Error        --tr:Failed to create persistent connection to ADMIN$ shared folder on host [<servername>].
Error        --tr:Failed to install service [VeeamDeploySvc] was not installed on the host [<servername>]. (System.Runtime.InteropServices.COMException)
Error           at VeeamProxyClient.GenerateComException(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* excMsg, Int32 errHrCode)
Error           at VeeamProxyClient.RegenerateCLRException(exception* excBase)
 
                      

Cause

When a Windows Server is added as a Managed Server or added to a Protection Group, Veeam Backup & Replication checks if the Veeam Installer Service (VeeamDeploySvc) is present on the server. If the service is not accessible Veeam Backup & Replication will attempt to connect to the machine via the admin$ share to deploy the service.

Example: \\localhost\admin$

The "Access is Denied" error occurs because the user account specified is a local account, and UAC restricts remote access for local accounts.

If this error is encountered while using a Domain account that is a member of the Local Administrators group on the remote Windows machine, please create a Veeam Support case mentioning this article.

Solution

For Veeam Backup & Replication to add a remote Windows machine as a managed server or as part of a Protection Group, the user account used to connect to that remote machine must work with the UAC remote restrictions. The account must be either:

A domain account that is a member of the Local Administrators group.
The built-in account named Administrator.

Use Case Examples:

If the Windows machine being added to Veeam Backup & Replication is joined to a domain, a domain account that is a member of the Local Administrators group on the remote machine should be used to add the server to Veeam Backup & Replication.
If the Windows server being added to Veeam Backup & Replication is not joined to a domain, or there is a need to avoid using a domain account, the built-in account named Administrator must be used to add the server to Veeam Backup & Replication. Other local accounts will be restricted by UAC, even if they are members of the Administrators group.

Note: If the Administrator account has been renamed, it can be used as the unique SID that bypasses Remote UAC Restrictions is still valid.
If the Windows machine being added to Veeam Backup & Replication is not joined to a domain and is not a server OS, the built-in Administrator account will have to be enabled and a password set for it. Then, that account should be used to add the machine to Veeam Backup & Replication.

More information

If none of the provided solutions are viable, it is possible to disable UAC remote restrictions. This will allow local accounts other than Administrator to be used for remote access. This option should be considered a last resort as it involves disabling a Microsoft Windows OS security feature.

↧

Export report email from Veeam Explorer for Microsoft Exchange is sent in an unexpected language

July 14, 2021, 1:50 pm

≫ Next: Veeam Install Error - "Selected ... port is not available."

≪ Previous: "Access is Denied." when using a local account to add Windows machine to Veeam Backup & Replication

KB ID:	4188
Product:	Veeam Backup & Replication

Challenge

Export reports sent by Veeam Explorer for Microsoft Exchange are illegible or unexpectedly contain Chinese characters.

Cause

The issue is caused by an encoding conflict. By default, Veeam Explorer for Microsoft Exchange uses UTF-16 character encoding, and the issue appears under following circumstances:

Use of Mimecast or Thunderbird
Office 365 organization located in Microsoft Azure China or Germany regions.

Solution

Export Report encoding can be changed for Veeam Explorer for Microsoft Exchange.

To change Export Report email encoding, perform the following:

Navigate to the folder %programdata%\Veeam\Backup\ExchangeExplorer\
Create a new file named Config.xml (If the Config.xml file already exists, edit it.)
Enter the following text:

 
                 <Veeam>
<Email MessageHeadersEncoding="UTF-8" MessageSubjectEncoding="UTF-8" MessageBodyEncoding="UTF-8" />
</Veeam> 
                

Example Config.xml

Save the Config.xml file
Perform an Export and confirm the Export Report email is legible

More information

A similar issue may occur with Veeam Backup for Microsoft Office 365 and is documented in https://www.veeam.com/kb2692.

↧

Veeam Install Error - "Selected ... port is not available."

July 15, 2021, 1:31 pm

≫ Next: Release Notes for Hitachi Plug-In for Veeam Backup & Replication (1.0.66)

≪ Previous: Export report email from Veeam Explorer for Microsoft Exchange is sent in an unexpected language

KB ID:	4189
Product:	Veeam Disaster Recovery Orchestrator, Veeam ONE, Veeam Backup & Replication, Veeam Service Provider Console

Challenge

During the initial installation of Veeam applications, the install wizard has a page where service ports may be specified. When moving to the next page of the install wizard, an error may be displayed regarding a Selected port not being available.

Expand each Veeam product name below for specific error text examples.

Veeam Backup & Replication

Selected Veeam Backup Catalog service port is not available.
Selected Veeam Backup & Replication service port is not available.
Selected Veeam Backup & Replication secure connections port is not available.
Selected RESTful API service port is not available.

Veeam Backup Enterprise Manager

Selected website HTTP port is not available.
Selected website HTTPS port is not available.
Selected Veeam Backup Restful API service HTTP port is not available.
Selected Veeam Backup Restful API service HTTPS port is not available.
Selected Veeam Backup Enterprise Manager service port is not available.
Selected Veeam Backup Catalog service port is not available.

Veeam ONE

Selected is not available.
Note: This error may be related to Communication Port or Internal Web API Port.
Selected Veeam ONE website port is not available.
Selected Veeam ONE agent port is not available.

Veeam Availability Orchestrator Setup

Selected Veeam Backup Catalog service port is not available.
Selected Veeam Backup & Replication service port is not available.
Selected Veeam Backup & Replication secure connections port is not available.
Selected Veeam Backup RESTful API service port is not available.
Selected Reporter web site port is not available.
Selected Veeam ONE agent port is not available.
Selected Veeam ONE communication port is not available.
Selected Veeam ONE Web API port is not available.
Selected Veeam Availability Orchestrator Server service port is not available.
Selected Veeam Availability Orchestrator Server WCF service port is not available.
Selected Veeam Availability Orchestrator Web UI port is not available.

Veeam Service Provider Console

Selected Veeam Service Provider Console communication port is not available.
Selected Veeam Service Provider Console management port is not available.
Selected Veeam Service Provider Console website and RESTful API v3 port is not available.
Selected Veeam Service Provider Console RESTful API v2 port is not available.
Selected communication port for ConnectWise Manage plugin is not available.

Cause

Upon clicking [Next] on the page of the installer where ports are defined, the installer checks if the specified ports are in use. The pop-up error occurs If a port is detected as being in use.

Solution

Identify and terminate the process using the port related to the error, then proceed with the installation of the Veeam software.

The following PowerShell script can be used to identify the process identifier number (PID) and process name using the specified port.

 
                 Get-Process -Id (Get-NetTCPConnection -LocalPort 9393).OwningProcess | ft Id,ProcessName 
                

For environments where PowerShell has been disabled, the following command can be used to determine the PID of the process using the port.

netstat -nbao | find "9393"

The examples above are for the error "Selected Veeam Backup Catalog service port is not available." and assume the default port of 9393.

↧

Release Notes for Hitachi Plug-In for Veeam Backup & Replication (1.0.66)

July 21, 2021, 12:48 pm

≫ Next: Missing vCenter entries in settings for vCloud Director

≪ Previous: Veeam Install Error - "Selected ... port is not available."

KB ID:	4191
Product:	Veeam Backup & Replication 11, Veeam Backup & Replication 10a

Requirements

Before installing Hitachi Plug-In, make sure that you are running Veeam Backup & Replication version 10.0.0.4461 or later. To check the version, open the main menu of the Veeam Backup & Replication console and select Help > About.

Hitachi Plug-In for Veeam Backup & Replication supports integration with the following storage systems:

VSP E590, E790, E990 (93-03-01-60/00 or later),
VSP F350, F370, F700, F900 (88-07-01-x0/00 or later),
VSP G350, G370, G700, G900 (88-07-01-x0/00 or later),
VSP 5000 series (90-05-01-00/00 or later)

Follow detailed instructions on configuring the Hitachi Plug-in and the storage system in the Hitachi Documentation.

Known Issues

The following is a list of known major issues for Hitachi Plug-In for Veeam Backup & Replication. If you experience any issue listed below, contact Hitachi support directly.

Adding Hitachi storage to the Veeam Backup & Replication infrastructure by Service Processor (SVP) IP is not supported but is allowed by this plug-in version. Make sure you are using one of the CTL1/CTL2 IP addresses to add the storage.
Note: This limitation does not apply to VSP 5000 series.
Hitachi Plug-In does not return information about volumes that are not mounted to a host. To perform a restore from snapshots residing on such volumes, mount a volume to a host and perform a rescan in the Veeam Backup & Replication console. For details, see Rescanning Storage Systems.
This plug-in version does not support Freeze-only snapshots. If you want to enable VM processing using VMware snapshots, contact Veeam support to change the value of a dedicated registry key.
If you make any changes to host groups/iSCSI targets configuration after at least one restore operation, you must manually restart the Veeam Backup Service. The service restart will refresh the plug-in cache, and the configuration changes will be updated.
After deleting a snapshot, logical device (LDEV) records with the _DEL suffix may remain on storage until the next storage rescan operation. However, such snapshots can be exported during rescan and displayed in the storage infrastructure UI as regular volumes. To avoid issues, you can manually delete or unexport such snapshots.
If jobs and rescan operations are running in parallel or at the moment when the storage system is processing other tasks, the operations may fail.
Hitachi Plug-In does not support backing up of failover clusters using Veeam Agent for Windows.
Veeam Backup Service restart causes subsequent Veeam Agent for Windows job to fail. The issue occurs because the job triggers storage information caching, and it exceeds the VSS freeze timeout.
Ensure there are at least two FC ports available on the storage; configurations with a single FC port are not supported.

Download Hitachi Plug-In 1.0.66

MD5: 8bc9d3698500e563438f04251b56cfcc
SHA1: f3101cfff56daadffa53d25e9b2e8d921bc21e92

↧

Missing vCenter entries in settings for vCloud Director

August 3, 2021, 7:12 am

≫ Next: Release Notes for HPE XP Plug-In for Veeam Backup & Replication 1.0.66

≪ Previous: Release Notes for Hitachi Plug-In for Veeam Backup & Replication (1.0.66)

KB ID:	4193
Product:	Veeam Backup & Replication, Veeam Cloud Connect

Challenge

When adding/editing vCloud Director Server in Veeam Backup & Replication the vCenter Servers list is missing vCenter entries.

The console log contains the following errors:

 
                 Error Failed to retrieve VC info
Error Failed to parse GUID from string 
Error Guid should contain 32 digits with 4 dashes 
                

Cause

This is related to a known issue in VMware Cloud Director version 10.2.1 and earlier. API calls to retrieve the vCenter Server information result in the VMware Cloud Director API incorrectly returning a URL instead of the expected UUID.

This can be verified using either of the following methods:

Verify using SQL query aginst vCloud Director database

execute the following SQL query against the vCloud Director database:

select name, uuid from virtual_center;

Example output:

 
                       name   | uuid
----------------------------------------------
testvc | 0034117e-b58b-4aca-8f96-50774aba6d1f
newvc  | https://<url>/sdk 
                      

In this example, the first entry has a UUID as expected, and the second entry is a URL in the UUID field.

Verify issue using vCloud Director API

Use a GET request to retrieve the representation of a registered vCenter server.

GET /admin/extension/vimServer/{id}
^{(Click for more information.)}

Example output:

Correct UUID format:

< vmext:Uuid > D9658206-D7AA-4D80-8E38-5328A39ABDD4 </ vmext:Uuid >

Problematic output:

< vmext:Uuid > https://vcloud.prod.local </ vmext:Uuid >

Solution

VMware has corrected this in vCloud Director 10.2.2 and 10.3.

The fix is preventative only and will not retroactively correct invalid entries.

To resolve this error and update the invalid entries, the following steps must be performed:

Upgrade vCloud Director (together with its database) to 10.2.2, 10.3, or later.
Reconnect the affected vCenter in vCloud Director.
This action will update the invalid database entry.

Repeat Step 2 for each vCenter affected by this issue.

If the issue persists after performing the steps listed above and the database still contains non-GUID entries in the UUID field, please get in touch with VMware support.

More information

VMware BugId: 2680344

↧

Challenge

Cause

Solution

Install Plug-in

Configuration

Connect to an existing appliance

Deploy a new appliance

Add Repository

Manage Appliances

More Information

Challenge

Please note that this utility is provided as a courtesy, and is not supported by Veeam Technical Support. Use at your own risk.This tool cannot fix jobs targeting a Cloud Connect repository. You must perform an Active Full backup.

Cause

Solution

More Information

Challenge

Cause

Solution

Example

More Information

Challenge

Cause

Solution

More Information

Challenge

Product Information:

Solution

Product Details:

Veeam testing configuration:

Job Settings:

Repository Settings:

Vendor recommended configuration:

Challenge

Cause

Solution

Common Workarounds

Registry Settings

Additional Troubleshooting

Challenge

Solution

More information

Challenge

Cause

Solution

More information

Challenge

Cause

Solution

Requirements

What's New

Solution

Requirements

New Features

Resolved Issues

Known Issues

Solution

1. Linux machine cannot boot from USB stick with Veeam Recovery Media that is created using third-party tools

2. Some hardware does not work with the Veeam Recovery Media

3. Patched Recovery ISO does not start veeamservice on boot

Challenge

Cause

Solution

More information

Objective

Solution

More information

Challenge

Cause

Solution

Semi-Automated Solution

Manual Solution

For Microsoft Windows 7, an additional step is required

More information

Challenge

Cause

Solution

Use Case Examples:

More information

Challenge

Cause

Please note that this utility is provided as a courtesy, and is not supported by Veeam Technical Support. Use at your own risk.

This tool cannot fix jobs targeting a Cloud Connect repository. You must perform an Active Full backup.