Quantcast
Channel: Veeam Support Knowledge Base
Viewing all 4469 articles
Browse latest View live

HCL - QNAP TS-x83XU

$
0
0

Challenge

VeeamReadyRepo

Product Information:

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

Solution

Product Details:

Model number: TS-1283XU-RP
Storage Category: RAID Storage Array
Drive quantity, size, type: 7 – 8TB SATA drives
Storage configuration: RAID5
Firmware version: 4.4.2.1320
Connection protocol and speed: NFS 10 GbE
Additional support: All models and configurations of TS-x83XU-RP with specifications equivalent or greater than the above

General product family overview:

The Intel® Xeon® E based TS-1283XU-RP enterprise NAS with up to 64 GB DDR4 ECC (Error Correcting Code) memory delivers server-grade performance with dependable reliability. It features 10GbE SmartNIC controllers that not only fulfill bandwidth-demanding applications but also support iSER to offload CPU workloads with boosted virtualization performance, while PCIe expansion allows for installing graphics cards to empower video surveillance, virtualization and AI applications.

 

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: 10.0.0.4461 P1

Job Settings:

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

Repository Settings:

Repository Type: NFS Share
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)

HCL - Quantum ActiveScale

$
0
0

Challenge

VeeamReadyObject

Product Information:

Company name: Quantum Corporation
Product Family: ActiveScale
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: P100
Storage Category: S3 compatible object storage
Drive quantity, size, type: 72 – 10TB SAS HDD
Storage configuration: ActiveScale is a software defined object store. Each drive is treated as an individual storage unit. Data protection and durability is achieved by erasure encoding objects and storing the “shards” over multiple disks.
Firmware version: 5.5.3
Connection protocol and speed: 6 – 10GbE network interfaces
Additional support: All models and configurations of ActiveScale for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
ActiveScale is Quantum’s object storage system that provides a data-forever storage infrastructure. ActiveScale was designed from the ground up as a self-healing, highly scalable, object storage system. The ActiveScale system architecture accommodates storing primary copy of multi-petabyte-scale datasets that are highly durable and facilitates long-term data retention with minimal administrative overhead.

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461 P2

 

Vendor recommended configuration:

Vendor Settings:

  • Factory defaults were used for all testing

HCL - Quantum Scalar i500

$
0
0

Challenge

VeeamReadyTape

Product Information:

Company name: Quantum Corporation
Product Family: Scalar Tape Devices
Status: Veeam Ready - Tape
Classification Description: Tape solution where available hardware features have been tested to work with Veeam.

Solution

Product Details:

Model number: i500
Library Firmware Version 710G.GS007
Drive firmware version: IBM LTO7 and IBM LTO8 Firmware: K4K4
Driver for tape drive: IBM IBMTape.w19_6268-x64_WHQL_Cert
Driver for media changer: IBMTape.w19_6268-x64_WHQL_Cert
Media type tested: LTO8

General product family overview:

Scalar libraries are the intelligent choice for archiving applications and long-term data retention. Proactive and automated monitoring and management reduces administration time and service interruptions keeping IT staff focused on key business objectives.

 

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461 P2

Veeam Backup for Microsoft Office 365 4c cumulative patch KB3222

$
0
0

Challenge

Veeam Backup for Microsoft Office 365 4c cumulative patch KB3222.

Cause

Please confirm you are running Veeam Backup for Microsoft Office 365 build 4.0.1.531 prior to installing this cumulative patch KB3222. You can check this under Help > About in Veeam Backup for Microsoft Office 365 console. After upgrading, your build version will change to 4.0.1.545.

As a result of on-going R&D effort and in response to customer feedback, cumulative patch KB3222 provides a set of enhancements and bug fixes, the most significant of which are listed below:

Enhancements:

  • Optimized reading from object storage repository to reduce the cost of querying the first 100 items in a folder when exploring backups with Veeam Explorers.
  • Parallel processing of requests for obtaining used space in backup repositories initiated via PowerShell or REST API on multiple proxies.
  • Reduced backup times to object storage repositories targets when processing SharePoint and OneDrive for Business items with thousands of versions.

Resolved Issues

  • After updating to Veeam Backup for Microsoft Office 365 4c (build 4.0.1.531) backups start to fail with the “Proxy offline time exceeded” error. For more details, see KB3216.
  • Under certain conditions, the backup proxy server sends ‘Success’ notifications about backup job completion results for backup jobs failed with the “Proxy offline time exceeded” error.
  • Unable to update certificate information for S3 Compatible object storage after the trusted certificate has been changed and a backup repository extended to such object storage goes to the ‘Invalid’ state.
  • OneDrive restore in the Modern Authentication mode fails with the “Cannot connect to Office 365” error.
  • Backup job initiated with the /v4/Jobs/{backup_job_id}/action REST API request performs full backup sync instead of incremental sync.
  • In the UI, changes to the schedule of applying retention policy settings for existing backup repositories are not saved.
  • SharePoint backup fails with the “The Attachments column does not exist. It may have been removed by another user” error.
  • Under certain conditions, in the Modern Authentication mode with legacy protocols enabled, Public Folder mailbox backup fails with the “Too many concurrent connections opened. Cannot open mailbox” error.

Solution

To install the cumulative patch KB3222:
  • Download VeeamBackupOffice365_4.0.1.545_KB3222.zip
  • Execute VeeamBackupOffice365_4.0.1.545_KB3222.msp as administrator on the Veeam Backup for Microsoft Office 365 server.

If there are any remote proxies in your environment, please update those as described here.

More Information

[[DOWNLOAD|DOWNLOAD|https://www.veeam.com/download_add_packs/backup-microsoft-office-365/kb3222/]]
MD5: a04037ee1830e578e3329c8932225eef
SHA-1: 9c075746fbb324d6a3695b5641e4a535b29ace5a

Enable SQL Database exclusions from application-aware image processing

$
0
0

Challenge

An SQL Database can be excluded from Veeam Application-Aware image processing

Solution

The solution below will instruct you on how to enable and use the DBExclusion menu that is built-in to Veeam Backup & Replication v7 or later.

  1. Connect to the server where Veeam Backup & Replication is installed
  2. Close any open Veeam Backup & Replication console windows.
  3. Open Regedit.exe
  4. Navigate to the key HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
  5. Add a new DWORD ‘EnableDBExclusions’
  6. Set the Value to 1
    User-added image
  7. Close the Registry Editor and open Veeam Backup & Replication
  8. Open “Database Exclusions” from the Main Menu
    User-added image
  9. In the window that pops up, click Add.
  10. Specify the DNS name (case sensitive) or the IP address and the instance name (case sensitive) containing the data that you wish to exclude from VSS Freezing and being Quiesced.
  11. Specify the Database name (case sensitive) that you wish to exclude from application-aware image processing.
    User-added image

More Information

NOTE: The key works only for Microsoft SQL server databases.

Veeam Backup for Microsoft Office 365 4c cumulative patch KB3222

$
0
0

Challenge

Veeam Backup for Microsoft Office 365 4c cumulative patch KB3222.

Cause

Please confirm you are running Veeam Backup for Microsoft Office 365 build 4.0.1.531 prior to installing this cumulative patch KB3222. You can check this under Help > About in Veeam Backup for Microsoft Office 365 console. After upgrading, your build version will change to 4.0.1.545.

As a result of on-going R&D effort and in response to customer feedback, cumulative patch KB3222 provides a set of enhancements and bug fixes, the most significant of which are listed below:

Enhancements:

  • Optimized reading from object storage repository to reduce the cost of querying the first 100 items in a folder when exploring backups with Veeam Explorers.
  • Parallel processing of requests for obtaining used space in backup repositories initiated via PowerShell or REST API on multiple proxies.
  • Reduced backup times to object storage repositories targets when processing SharePoint and OneDrive for Business items with thousands of versions.

Resolved Issues

  • After updating to Veeam Backup for Microsoft Office 365 4c (build 4.0.1.531) backups start to fail with the “Proxy offline time exceeded” error. For more details, see KB3216.
  • Under certain conditions, the backup proxy server sends ‘Success’ notifications about backup job completion results for backup jobs failed with the “Proxy offline time exceeded” error.
  • Unable to update certificate information for S3 Compatible object storage after the trusted certificate has been changed and a backup repository extended to such object storage goes to the ‘Invalid’ state.
  • OneDrive restore in the Modern Authentication mode fails with the “Cannot connect to Office 365” error.
  • Backup job initiated with the /v4/Jobs/{backup_job_id}/action REST API request performs full backup sync instead of incremental sync.
  • In the UI, changes to the schedule of applying retention policy settings for existing backup repositories are not saved.
  • SharePoint backup fails with the “The Attachments column does not exist. It may have been removed by another user” error.
  • Under certain conditions, in the Modern Authentication mode with legacy protocols enabled, Public Folder mailbox backup fails with the “Too many concurrent connections opened. Cannot open mailbox” error.

Solution

To install the cumulative patch KB3222:
  • Download VeeamBackupOffice365_4.0.1.545_KB3222.zip
  • Execute VeeamBackupOffice365_4.0.1.545_KB3222.msp as administrator on the Veeam Backup for Microsoft Office 365 server.

If there are any remote proxies in your environment, please update those as described here.

More Information

[[DOWNLOAD|DOWNLOAD|https://www.veeam.com/download_add_packs/backup-microsoft-office-365/kb3222/]]
MD5: a04037ee1830e578e3329c8932225eef
SHA-1: 9c075746fbb324d6a3695b5641e4a535b29ace5a

How to Deploy FLR Relay Proxy

$
0
0

Challenge

During file-level restore, you want to use your own TLS certificate to secure communication between the web browser on a local machine and the Veeam Backup browser on a worker instance.

Additionally, you want the Veeam Backup browser link to be static and include your own public DNS name instead of a public DNS name of a worker instance.

Solution

To use your own TLS certificate during file-level restore and have the static Veeam Backup browser link:
  1. In AWS CloudFormation, deploy and configure an EC2 instance that will act as an FLR relay proxy.
    In stack settings, you will need to specify the path to the TLS certificate and desired public DNS name. To obtain the stack template file, contact Veeam Customer Support.
  2. In worker instance settings, specify the FLR relay proxy for each AWS region where you plan to perform file-level restore.
    During file-level restore, Veeam Backup for AWS will route traffic to and from the launched worker instance through the specified FLR relay proxy.
Prerequisites
  • Valid TLS certificate, for example, obtained from Let’s Encrypt.
    The TLS certificate must be located in an S3 bucket folder.
  • Public DNS name that you own, for example, flr.domain.com.

Deploying FLR Relay Proxy in AWS CloudFormation

 

In AWS CloudFormation, for each AWS region where you plan to use the FLR relay proxy, complete the following steps:

  1. Launch the Create Stack wizard as described in AWS Documentation.
  2. At the Specify template step of the wizard, upload a template file obtained from Veeam Customer Support.
  3. At the Specify stack details step of the wizard, specify the following settings:
    1. In the Stack name field, specify a name for the EC2 instance that will act as an FLR relay proxy.
      User-added image
    2. From the Key Pair drop-down list, select a key pair that will be used to authenticate against the FLR relay proxy.
      You will require the specified key pair if you want to connect to the proxy over SSH.
    3. [Optional] In the SSH Location field, specify the IPv4 address range from which you want to access the FLR relay proxy over SSH.
    4. In the HTTPS Location field, specify the IPv4 address range from which you plan to access the Veeam Backup browser during file-level restore.
    5. From the VPC and Subnet drop-down lists, select an Amazon Virtual Private Cloud (Amazon VPC) and subnet to which the FLR relay proxy must be connected.
    6. In the DNS Name field, specify the public DNS name that you own and want to include in the Veeam Backup browser link.
      User-added image
    7. In the S3 bucket with certificate field, specify the bucket folder name where the TLS certificate you want to use is located (without ‘s3://’).
      For example, MyBucketName/certificates
    8. In the Certificate file name field, specify the name of the certificate file that is located in the specified bucket folder.
      For example, certificate.pem
    9. In the Key file name field, specify the name of the private key file that is located in the specified bucket folder.
      For example, privatekey.pem
      User-added image
  4. At the Configure stack options step of the wizard, specify AWS tags, IAM role permissions and other additional settings if necessary, and then click Next.
  5. At the Review step of the wizard, review the specified settings, select the I acknowledge that AWS CloudFormation might create IAM resources check box, and click Create stack.
  6. Associate the DNS name specified at step 3.f with the Elastic IP address that is assigned to the FLR relay proxy.
    To view the public IP address of the FLR relay proxy:
    1. Open the Amazon EC2 console.
    2. In the navigation pane, click Instances.
    3. Find and click your FLR relay proxy.
    4. On the Description tab, on the right of IPv4 Public IP, you will find the IP address of the FLR relay proxy.
  7. Wait until the FLR relay proxy is deployed.
    You can track the proxy deployment progress in the execution log at http://<IPaddress-of-your-proxy>:80.

After successful installation of proxy components, the proxy will automatically shut down.
If this does not happen, check the proxy deployment status in the execution log at http://<IPaddress-of-your-proxy>:80 and contact Veeam Customer Support.
 

Specifying FLR Relay Proxy in Advanced Worker Instance Settings

 

Once the FLR relay proxy is deployed, access Veeam Backup for AWS and complete the following steps:

  1. At the top right corner of the Veeam Backup for AWS window, click Configuration.
  2. In the configuration menu on the left, click Workers.
  3. On the Advanced tab, click Add.
    Veeam Backup for AWS will launch the Add Region wizard.
  4. At the Region step of the wizard, specify the AWS region in which the FLR relay proxy is deployed.
    User-added image
  5. At the Worker Settings step of the wizard:
    1. Click Select and choose the necessary FLR relay proxy from the list.
    2. In the DNS Name field, enter the DNS name that you specified in FLR relay proxy settings.
    3. From the Security Group drop-down list, select a security group to which the FLR relay proxy will be connected during file-level restore.
      User-added image
  6. At the Summary step of the wizard, review the specified settings and click Finish.

Veeam Backup for AWS will automatically use the configured FLR relay proxy when you perform file-level restore in the AWS region where the proxy is deployed.

More Information

Should you have any questions on FLR relay proxy deployment or configuration, please contact Veeam Customer Support.

 

How to Move the VBRCatalog Folder

$
0
0

Challenge

The VBRCatalog folder needs to be moved.

Cause


 

Solution

The following steps are to be performed on the server where Veeam Backup & Replication is installed.


  1. Make sure all jobs are stopped and constantly running jobs are disabled.
  2. Stop all Veeam services (PowerShell: gsv Veeam* | spsv)
    gsv Veeam* | spsv
  3. Move the VBRCatalog folder to the new location.†
  4. Recreate the Share
    1. Open Computer Management
    2. Navigate to [System Tools] > [Shared Folders] > [Shares]
    3. From Menu select [Action] > [New Share...]
    4. Select the new folder path to where the VBRCatalog was moved
    5. On the next page of the wizard the share name should be VBRCatalog
    6. On "Shared Folder Permissions" page select [Customize permissions]
    7. Remove "Everyone"
    8. Add "Administrators"
      Note: the Location selected when specifying Administrators must be the Veeam Server, not the domain.
    9. The Permissions should now list Adminsitrators with only Read Allow permission.
    10. Press OK, and Finish (twice) to complete recreation of the share.
  5. Change the location in the registry.
    1. Open Regedit
    2. Navigate to HKLM\SOFTWARE\Veeam\Veeam Backup Catalog
    3. Find the REG_SZ entry named "CatalogPath"
    4. Change the Value data to match the new VBR catalog location.
  6. Start all Veeam services (PowerShell: gsv Veeam* | sasv)
    PowerShell: gsv Veeam* | sasv

 

More Information

† If the VBRCatalog folder is missing or was deleted, create a new folder named "VBRCatalog" in the desired new location.


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

$
0
0

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:
  1. Open the Veeam Backup & Replication console.
  2. 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

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

Release Notes for Western Digital Plug-In for Veeam Backup & Replication 1.0.81

$
0
0

Challenge

Release Notes for Western Digital Plug-In for Veeam Backup & Replication 1.0.81

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

 

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:
  1. Open the Veeam Backup & Replication console.
  2. In the main menu, click Help and select About.

Solution

This update features the following enhancement:
  • Added support for IntelliFlash OS version 3.10.1.x or later.

More Information

This update has been superseded by Tintri IntelliFlash Plug-In for Veeam Backup & Replication 1.0.85

Release Information for Veeam Availability Orchestrator v3

$
0
0

Challenge

Release Information for Veeam Availability Orchestrator v3.

Cause

Please confirm that you are running version 2.0 (build 2.0.1.1403) or later prior to upgrading. You can check this in the VAO UI | Administration tab| About. To upgrade from earlier versions, please contact our Customer Support. After upgrading, your build number will be 3.0.0.1770.

Solution

Please refer to What’s New and Release Notes documents for the detailed information about this release.

Be sure to review the upgrade section of the corresponding user guide closely prior to upgrading.

More Information

[[DOWNLOAD|DOWNLOAD|https://www.veeam.com/send_license/availability-orchestrator/]]
MD5: 681c737541ba34eb6d35040604fbccf4
SHA1: f3f972c991d6d984655208d3e954ba63718d85ad

How to Clean Up the Credentials Manager in Veeam Backup & Replication

$
0
0

Challenge

Over time there may become a number of duplicate or outdated credentials saved in the Credentials Manager of Veeam Backup & Replication. This guide will attempt to document a process for reviewing and cleaning up the Credentials Manager.

Solution

Remember: No changes to the Credentials Manager account list are saved until [OK] is pressed. So if an account is accidentally removed, click [Cancel] and the account will not be removed from the database.


How to open the credentials manager

From the main menu in the top left corner of the Veeam Backup & Replication console select [Manage Credentials]


Phase 1: Removing unused Accounts

Go through each entry and remove those which are not in use* and will not be needed in the future.

*You can verify is an account is in use by selecting it and clicking edit, if it is in use a window will stop you from editing the entry and show you where that account is assigned.
 

Note: The software will not allow you to remove an entry which is in use.

Remember to press [OK] and close the Manager Credentials window to save the settings before proceeding.
 


Phase 2: Removing Duplicate Entries

If duplicate entries are present, edit each of them and review the list of locations where that account is assigned.

Determine which of the duplicate entries is used in the most places. Edit that one, click [Yes] when presented with the list of where it is in use, and change its description to something distinct.

Now edit the duplicate(s) and take note of where the duplicate credential(s) are in use. In most cases the "Name" and "Description" column will provide enough information to identify where it is set.

Navigate around the software to the different locations and change those objects to use the account you marked with a distinct description.

Once all places where the duplicate credential was in use have been corrected, it will be possible to Remove the duplicate entry.

More Information

One of the trickiest entries can be one that states "<Server Name> (<Job Name>)" and lists as "Guest OS credentials for Backup Job". 

This means that the credential has been specifically assigned to that server inside the job settings under either of these locations.

  • Job Settings > [Guest Processing] > [Credentials...]


     
  • Job Settings > [Guest Processing] > [Applications...] > (Edit the specific server) > [Oracle] tab


     
  • For Veeam Agent for Windows Backup jobs check the SQL tab next to the Oracle tab mentioned above.

 

 

Quick Tip: A quick method of clearing all unused credentials is to highlight all entries, and then hold control and deselect the "Helper appliance", "Tenant-side network extension appliance", and "Azure helper appliance". Once those three are deselected, the [Remove] button can be clickable and all credentials not presently assigned will be removed.

Release Information for Veeam Availability Orchestrator v3

$
0
0

Challenge

Release Information for Veeam Availability Orchestrator v3.

Cause

Please confirm that you are running version 2.0 (build 2.0.1.1403) or later prior to upgrading. You can check this in the VAO UI | Administration tab| About. To upgrade from earlier versions, please contact our Customer Support. After upgrading, your build number will be 3.0.0.1770.

Solution

Please refer to What’s New and Release Notes documents for the detailed information about this release.

Be sure to review the upgrade section of the corresponding user guide closely prior to upgrading.

More Information

[[DOWNLOAD|DOWNLOAD|https://www.veeam.com/send_license/availability-orchestrator/]]
MD5: 681c737541ba34eb6d35040604fbccf4
SHA1: f3f972c991d6d984655208d3e954ba63718d85ad

"Reprotect storage volumes after failover" operation fails during storage plan execution

$
0
0

Challenge

If you enable the "Reprotect storage volumes after failover" option when running a storage plan, Veeam Availability Orchestrator triggers the operation of resynchronizing the SnapMirror relationship in the reverse direction.

In a reverse resynchronization operation, NetApp reverses the roles of the source and destination volumes, and the source volume becomes a copy of the destination volume. For more information on what a reverse resynchronization operation does, see the NetApp ONTAP Documentation Center.

Cause

The reverse resynchronization operation may fail to complete successfully if the names of SVMs involved in the storage failover process are used as aliases.

To check whether the name of an SVM is used as an alias, log in to the NetApp system (for both participants of the protection relationship) through the CLI interface and run the following command: vserver peer show. An alias is used if the command output displays the name of the Peer Vserver as name.*. Perform this step for both the source and destination SVMs.

Solution

To work around the issue, perform the reverse resynchronization operation manually.

Storage plan cannot leave the "Resetting (with sync process)" state

$
0
0

Challenge

After you undo or reset a storage plan, the plan acquires the "Resetting (with sync process)" state and cannot switch to another state.

Cause

In case you have a large infrastructure or in case any internal issues occur in the Veeam ONE database, the undo or reset operation may not complete quickly enough and may cause the plan to remain in the "Resetting (with sync process)" state.

Solution

  1. If the operation does not complete in 24 hours, the plan will be resetted automatically.
  2. Alternatively, you can reset the plan manually. For more information, see the Veeam Availability Orchestrator User Guide, section Resetting Storage Plans.

Release Notes for Veeam Backup & Replication 9.5 Update 3a

$
0
0

Challenge

Release Notes for Veeam Backup Replication 9.5 Update 3a

Cause

Please confirm that you are running version 9.5.0.580, 9.5.0.711, 9.5.0.802, 9.5.0.823, 9.5.0.1038, 9.5.0.1335 or 9.5.0.1536 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console. After upgrading, your build number will be 9.5.0.1922.
To upgrade from 9.0 or earlier version, download version 9.5 ISO image, and consult the User Guide's upgrade section.

Solution

As the result of an on-going R&D effort, and in response to customer feedback, Veeam Backup & Replication 9.5 Update 3a features a large number of enhancements, the most significant of which are listed below.

Platform support
  • VMware vSphere 6.7. Includes the new HTML5 version of vSphere Web Client plug-in for Veeam Backup & Replication, and asynchronous NBD/NBDSSL support for improved read performance of network transport mode with ESXi 6.7.
  • VMware vSphere 6.5 U2. This update introduces preliminary support by addressing all outstanding U2-specific compatibility issues that can be managed from the Veeam side. 
  • VMware vCloud Director 9.1. Update 3a provides full compatibility for all existing vCloud Director integration functionality.
  • VMware Cloud on AWS version 1.3 support and preliminary out-of-the-box compatibility with future VMC updates through removal of the API version match requirement. Additionally, support for processing virtual machines with dynamic disks has been added.
  • Microsoft Windows 10 April 2018 Update. Includes support as guest virtual machines and for installation of Veeam Backup & Replication and all of its components.
  • Microsoft Windows Server 1803. Update 3a provides Windows Server 1803 support as guest virtual machines, for installation of Veeam Backup & Replication remote components, and as a domain controller for Veeam Explorer™ for Microsoft Active Directory.
  • Microsoft Windows Server Hyper-V 1803. Update 3a provides Hyper-V 1803 support as a hypervisor host, including support for processing VMs with virtual hardware version 8.3.
  • Microsoft System Center Virtual Machine Manager 1801. Update 3a adds SCVMM 1801 support as a source for Microsoft Hyper-V VMs backup jobs.
  • Novell OES 2018. Update 3a adds support for file-level recovery from the updated NSS file system included in OES 2018.
VMware vSphere
  • Performance of Direct Storage Access (DirectSAN) and Virtual Appliance (Hot Add) transport modes has been improved for backup infrastructure configurations through optimizing system memory interaction.
Microsoft Azure
  • Added support for Direct Restore to Microsoft Azure for environments with ExpressRoute or site-to-site VPN connectivity to Azure, in which case proxy and helper appliances may have private IP addresses only. To enable, create AzurePreferPrivateIpAddressesForProxyandLinuxAppliance (DWORD, 1) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server.
Linux File Level Recovery
  • Added support for Linux SUID and SGID preservation to "Copy To" operation.
  • Added support for Btrfs volumes located on an LVM volume.
Primary Storage Integrations
  • Installing Universal Storage API plug-ins on each backup console (in addition to the backup server) is no longer required.
  • Storage snapshot-only vCloud Director backup jobs are now supported for all storage integrations which support storage snapshot-only jobs. Previously, it was supported for NetApp only.
  • Cisco HyperFlex integration will no longer delete the base sentinel snapshot during each job run to improve processing performance and reduce storage load.
Tape
  • Improved performance of enumeration in File to Tape jobs with very large number of files.
Veeam Cloud & Service Provider partners
Veeam Backup & Replication 9.5 Update 3a also includes enhancements and bug fixes for service providers offering Veeam Cloud Connect services, and managing backup servers with Veeam Availability Console. For the full change log, please see this topic on the private Veeam Cloud & Service Provider (VCSP) forum. Not a member of the VCSP forum? Click here to join.

Update 3a also resolves the following common support issues:
  • User interface performance has been improved for large environments, including faster VM search and lower CPU consumption while browsing through job sessions history.
  • Restores through Direct NFS transport should no longer produce corrupted VMDKs on storage devices with advanced NFS server implementations.
  • VeeamZIP™ operations should no longer consume a license.
  • Backup copy job should no longer trigger health checks outside of the scheduled start time when GFS retention is in use, and will behave more reliably in a few corner cases.
  • Incremental backup runs should no longer keep setting ctkEnabled VM setting to "true", resulting in unwanted events logged by vCenter Server.
  • SATA X:7 disks should no longer be skipped with backup jobs by default.
  • Windows file level recovery (FLR) should now process large numbers of NTFS reparse points faster and more reliably.
  • Linux FLR should now correctly process directories with . and \ symbols in their names. In addition, encountering a named pipe object should no longer cause FLR to hang.
  • Direct Restore to Microsoft Azure should now process Linux machines with EFI boot more reliably.
  • Veeam Agent for Microsoft Windows’ jobs should no longer fail when the backup server uses custom certificate.
  • Veeam Explorer for Storage Snapshots now supports VMs located on LUNs larger than 16TB.
  • An HPE 3PAR integration should now handle large number of concurrent jobs more reliably, thanks to multiple improvements implemented based on support cases.
  • An HPE StoreOnce Catalyst SDK host process will now be restarted automatically when a Catalyst API call hangs, preventing Veeam jobs from hanging as a result.
  • IBM SVC integration should no longer fail at collecting iSCSI adapters.

More Information

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

Alternatively, you can download the update package without backup agents here.

MD5 checksum for VeeamBackup&Replication_9.5.0.1922.Update3a.zip is 7EE1797D42B7E3479E99506E15FBA379
MD5 checksum for VeeamBackup&Replication_9.5.0.1922.Update3a_noagents.zip is 55DE657FEBCCF7904E7C0108629F44F4

IMPORTANT: If you start to receive warnings backing up Microsoft SQL Server VMs after installing the update, please review this article

Veeam Agent for Windows: How to Setup Exclusion and Inclusion Masks

$
0
0

Challenge

Veeam Agent for Microsoft Windows provides advanced capabilities of file filters. As a result, some files or folders will be excluded to the backup or, vice versa, only those objects which are specified in the filter will be included into the final backup point.

Cause

Underlying exclusion techniques have different specific factors which must be taken into account:
 
  • Veeam Agent uses various algorithms, some of them are based on VSS techniques we rely on (the job triggers communication with the FilesNotToSnapshot registry key which helps to exclude specific files from a shadow copy triggered by our backup followed by exclusions those files from our backup - we read data from VSS shadow copies, so as longs as files are excluded from the shadow copy, we won't process them too).
     
  • Those VSS exclusions are not implemented in specific job modes and we read all source data but copy only those data we specified in the backup set considering all file filters - this algorithm is implemented in the file-level job mode when individual folders are selected for the backup.

Unfortunately, techniques above have some limitations which could case some challenges with the file filters implementation.

Solution

This article describes basic file filter scenarios you may want to implement in your infrastructure.
All backup scenarios are implemented by using the file-level backup mode (it is the only backup mode that allows implementing file filters).

However, the file-level backup job may contain whole volumes and individual folders in it (it's called hybrid backup) - depending on a backup source, eventually, file filters may work differently. Scenarios below help to go through all possible points you may want to achieve.

  1. Backup one folder without one subfolder

  2. Exclude subfolder using environment variables

  3. Exclude files from backup using mask

  4. Exclude files and folders using wildcard mask in path

  5. Exclude files and folders using wildcard mask in file names

  6. Include files using wildcard mask in file names 

  7. Include only selected files in the backup

  8. Include files using wildcard mask and exclude some of them using wildcard mask

  9. Include files to backup which apply some convention

  10. Include some folder and exclude one or several subfolders

  11. Include folder and exclude subfolders using wildcard mask

  12. Include folder and exclude subfolders using environment variables

  13. Processing of exclusions when folder and volume are added

Backup one folder without one subfolder:

User-added image

Result: The resulting backup will contain all folders and files that reside on the volume C:\ except files that reside in the C:\excltest folder.

Exclude subfoler using environment variables:

User-added image

Exclusions are specified as the custom system environment variable ex1.

Result: The resulting backup will contain all folders and files that reside on the volume C:\ except files that reside in the C:\excltest folder which is defined the custom system variable ex1.

Veeam Agent for Microsoft Windows helps to implement all system environment variables as include and exclude masks, however, mind the following:

  • To specify include and exclude masks, you can use only system environment variables — variables defined for the Local System account on computers added to the backup job, and cannot use user environment variables (Veeam Agent works under the NT AUTHORITY\SYSTEM account, so all exclusions are treated accordingly).
  • You cannot use environment variables that contain multiple values or other environment variables to specify include and exclude masks, such setup is not supported.

Exclude files from backup using mask:

User-added image

Result: The resulting backup will contain all folders and files that reside on the volume C:\ except files that reside in folders whose names start with "1".

Exclude files and folders using wildcard mask in path:

User-added image

Result: Exclusions won't be applied because exclusions of folders with wildcards in the middle of the path are not supported (e.g., C:\excltest\*\2)
User-added image

However, there is the following workaround for it:

To exclude recursively the files from specific subfolders of the folder the OS mechanism can be utilized, so no need to apply Veeam job exclude filters:
User-added image

The registry key HKLM:\SYSTEM\ControlSet001\Control\BackupRestore\FilesNotToSnapshot contains the list of files which are excluded from the processing during the shadow copy creation, so we may apply the OS mechanism to exclude data from a VSS shadow copy followed by exclusions those files from our backup (we read data from VSS shadow copies, so as longs as files are excluded from the shadow copy, we won't process them too).
User-added image

In the example above, to exclude all files in subfolders named as “2” from C:\excltest\* the corresponding registry entries should be created. In some cases, manual adding all subfolders is not that straightforward because the number of folders is really huge.

As a workaround here is an example of the PowerShell script that upon the execution will add all such folders to the single registry value

$fold =(ls C:\excltest -Recurse -Directory).FullName | ? {$_ -like 'C:\excltest\*\2'} | % {"$_\* /s"}
New-ItemProperty -Path "HKLM:\SYSTEM\ControlSet001\Control\BackupRestore\FilesNotToSnapshot" -Name "Excl" -PropertyType MultiString -Value $fold
User-added image

The script adds all folders named as "2" recursively to FilesNotToSnapshot

As a result, the backup will contain all folders and files that reside on the volume C:\ except files that reside in folders which are defined by the mask C:\excltest\*\2.

The script above can be changed depending on your needs. Keep in mind that in case of a large number of excluded folders, MS Copy Optimization Writer, depending on available resources, may fail to exclude all data. Consider switching over to selecting only a specific folder as the backup source or thing through reducing the number of excluded folders. More details are in the article - https://www.veeam.com/kb2073

Please note that Veeam Technical Support does not provide the scripts on demand and does not troubleshoot custom scripts.

Include files using wildcard mask in file names:

User-added image

Result: The resulting Veeam Agent backup will contain all files residing in the specified folder except all files with the *.bak extension.

! C:\excltest here and below is a folder name, not a volume mount point mounted to a folder.

In case when the job is configured with the following parameters: 
User-added image

Result: The resulting Veeam Agent backup will contain all data residing on volume C:\, no exclusions will be applied.
 

Exclude files and folders using wildcard mask in file names:

User-added image

Result: The resulting Veeam Agent backup will contain all files residing in the specified folder except all files containing the *veea* in names (*veea* folders are not affected).

Include only selected files in the backup:

Result: The resulting Veeam Agent backup will contain all data residing on volume C:\, no include masks will be applied.

You cannot specify include masks if you add an entire volume in the backup. 

To specify file names and/or masks for file types that you do not want to back up proceed with the following scenario:
User-added image

Result: Veeam Agent for Microsoft Windows will create a backup only for selected files. Other files will not be backed up.

Include files using wildcard mask and exclude some of them using wildcard mask:

User-added image

Result: Veeam Agent for Microsoft Windows will include in the backup all files of the DOCX format that do not contain Test in their names.

Include files to backup which apply some convention:

User-added image

Result: Veeam Agent for Microsoft Windows will include in the backup all files in C:\New folder except those which fit this convention -Test_?_C.txt.
User-added image

Include some folder and exclude one or several subfolders:

User-added image

Result: The resulting Veeam Agent backup will contain all data residing in the specified folder C:\excltest except the folder “C:\excltest\1”.

Include folder and exclude subfolders using wildcard mask:

User-added image

Result: The resulting Veeam Agent backup will contain all data residing in the specified folder except all folders with the name starting with symbol “1”.
 

Include folder and exclude subfolders using environment variables:

User-added image

Result: The resulting Veeam Agent backup will contain all data residing in the specified folder except all folders defined by the custom system variable ex1.

As it states above, to specify include and exclude masks, you can use only system environment variables — variables defined for the Local System account on computers added to the backup job, and cannot use user environment variables (Veeam Agent works under the NT AUTHORITY\SYSTEM account, so all exclusions are treated accordingly).

You cannot use environment variables that contain multiple values or other environment variables to specify include and exclude masks, such setup is not supported.
 

Processing of exclusions when folder and volume are added:

User-added image

HCL - MinIO with Immutability

$
0
0

Challenge

VeeamReadyObject

Product Information:

Company name: MinIO
Product Family: MinIO
Status: Veeam Ready – Object with Immutability
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier object storage immutability features.

Solution

Product Details:

Model number: RELEASE.2020-07-12T19-14-17Z
Storage Category: S3 Compatible Object Storage
Drive quantity, size, type: 8 – 1.8TB HDD
Storage configuration: JBOD with default n/2 erasure coding enabled
Firmware version: 2 x 10Gbps links (LACP)
Additional support: All models and configurations of MinIO for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
MinIO is a high-performance, software defined, S3 compatible object store. MinIO was purpose-built to serve only objects and its single-layer architecture can run in user space and is easily containerized and can be orchestrated using Kubernetes. The software is scalable and offers resilience through inline erasure coding and bitrot protection. The software also contains a number of important security features including encryption for data in flight and at rest, object locking, auditing and identity management.

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461

Release Information for Veeam ONE 10a

$
0
0

Challenge

Release Information for Veeam ONE 10a (build 10.0.2.1094).

Cause

Please make sure you are running version 9.5.0.3801 (9.5 Update 3) or later prior to installing this update. You can check this under Windows > Programs and Features. After upgrade, your build will be version 10.0.2.1094.

Solution

As a result of ongoing R&D effort and in response to customer feedback, this update includes a set of bug fixes and new features, the most significant of which are listed below:
 
What's New

Veeam Backup for AWS and Veeam Backup for Microsoft Azure Support 

Veeam users utilizing cloud-native data protection for Amazon Web Services (AWS) or Microsoft Azure), now have visibility* into data protection status across all cloud VMs, regardless of their location. 

The unique benefits of cloud-native data protection support in Veeam ONE include: 
  • Monitoring and alerting. Veeam ONE users can now monitor backup and snapshot job status of cloud-based workloads via predefined alarms and notifications.  
  • Backup status reporting. Predefined Protected VMs report now includes VMs hosted in AWS and Microsoft Azure public. This helps users in verifying the data protection status for each discovered VM based on the agreed SLA.
* Requires Veeam Backup & Replication 10a or later and AWS Plug-In for Veeam Backup & Replication (now available) or Azure Plug-In for Veeam Backup & Replication (coming soon).

Enhancements 

Licensing 
  • License information dialog now displays weight multiplier for monitored workloads. 
  • License information dialog has been enhanced when installing a merged license key (sockets and instances). 
Security 
  • User authentication, when using internal Web API methods, has been enhanced. 
  • Code deserialization mechanism has been enhanced when using the Veeam Intelligent Diagnostics feature.

Resolved Issues

Server
  • Under certain conditions, Veeam ONE server can experience a deadlock situation when saving new data. 
  • Under certain conditions, Veeam ONE services fail to start after manipulation with the database. 
  • Object property collection task in Veeam ONE Reporter takes more time to complete the operation after upgrading from version 9.5. 
  • Object property collection task in Veeam ONE Reporter fails with a timeout for large-scale infrastructures.
  • Topology from a vCenter server fails to collect due to presence of VMs with more than 100 virtual disks attached.
Setup
  • Veeam ONE setup fails if the service account does not have “sysadmin” permissions on the specified Microsoft SQL Server instance. 
Upgrade
  • Upgrade of Veeam ONE (advanced deployment type) to v10 resets the list of collected performance counters to defaults.
  • When using Microsoft SQL Server Express, Veeam ONE upgrade to v10 may fail with the insufficient space for a database error message. 
Retention Policy 
  • Under certain conditions, deleted Nutanix VMs are not removed from the Veeam ONE database. 
Backup Reporting 
  • “Backup Infrastructure Custom Data” report fails to generate when using Turkish locale for the Veeam ONE server. 
  • “Backup Infrastructure Custom Data” report fails to generate when the Last Run Start Time property is selected in the custom filter. 
  • “Backup Infrastructure Custom Data” report does not show VM names for tape jobs. 
  • Under certain conditions, “Backup Infrastructure Custom Data” report fails to generate when “Computer” is selected as a reported object. 
  • Scale-out Backup Repository Configuration report shows less utilized extents in the “Top x Utilized Extents” chart in the summary section. 
  • Under certain conditions, extents moved out from the scale-out backup repository cannot be selected in the scope of Veeam Backup & Replication reports.  
  • “GFS Backup Files” report ignores the selected job list for data displayed on the summary page.   
Licensing 
  • VM processed by multiple monitored Veeam Backup & Replication servers is accounted multiple times in license usage statistics. 
  • Veeam ONE triggers a false-positive warning message when license capacity is reached, and exclusion rules for monitored objects are applied.
  • Under certain conditions, Veeam ONE license usage can be calculated incorrectly when the same VM is present in multiple backup jobs. 
  • Veeam ONE assigns license to all protected VMs regardless of their backup date, so that all VMs with backups older than 30 days are accounted for in usage statistics. 
  • Under certain conditions, Veeam ONE license verification fails with the “License signature is invalid” error message. 
Monitoring
  • Under certain conditions, performance alarms are not triggered for monitored in-guest OS processes. 
  • "Heartbeat is missing for VM" alarm cannot be configured with a monitoring period of less than 15 minutes. 
  • “Suspicious incremental backup size” alarm is not triggered for new backup job sessions if this alarm is already in the triggered state.
  • “Suspicious incremental backup size” alarm is automatically resolved when VeeamDCS service is restarted. 
  • “Suspicious incremental backup size” alarm does not account for per-VM backup chains and does not display VM names in the alarm description. 
  • Under certain conditions, memory usage for Hyper-V VMs is displayed incorrectly on the VMs tab in Veeam ONE Monitor Client. 
  • Under certain conditions, data collection job for System Center Virtual Machine Manager (SCVMM) may fail when VM checkpoints return invalid data. 
  • Limited scope users can see resource pools, vApps, and other vSphere objects that do not belong to their scope when using the alarm management tab. 
Dashboards
  • When editing a custom Veeam Backup & Replication dashboard, it may disappear from the UI if there is no Veeam Backup & Replication server added to Veeam ONE. 
Categorization 
  • Grouping expression with the “Replace” function will not categorize any objects if the condition is replaced with an empty string.

More Information

[[DOWNLOAD|DOWNLOAD|https://www.veeam.com/download_add_packs/virtualization-management-one-solution/10a/]]

MD5: d7b9602d2d542971132e1dd0720a7b3b
SHA-1: 9441d3d9e98a98fc5fc0ac1d1cd5571f30b4713f

Veeam ONE database calculator

$
0
0

Challenge

The calculator will assist you in planning the deployment taking into account all major factors that impact the database size.

Cause

Veeam ONE database sizing calculator will help you calculate the expected size of databases to store historical data for one year and estimate the following deployment requirements:                                
  • Disk space required to store VMware vSphere historical data 
  • Disk space required to store Microsoft Hyper-V  historical data 
  • Disk space required to store Veeam Backup & Replication historical data"                                
Calculation results are based on the following parameters you need to provide:                                 
  • Virtual infrastructure inventory (number and configuration of objects in your virtual infrastructure)
  • Veeam Backup & Replication infrastructure inventory (number of jobs, VMs in the backup job and job schedule)"     

Solution

Download the calculator here.

To estimate disk space required for the database:                                
  1. Investigate your virtual and backup infrastructures to find out the number of hosts, clusters, virtual machines, datastores to monitor as well as their configuration parameters.                                
  2. On the Calculator worksheet in the Parameters column,  enter information about your infrastructure inventory, job schedule and number of protected VMs. Note that the green text color in cells indicates user-input values; the grey text color indicates that the values should not be changed.                                
The calculated results are available in the Results column on the Calculator worksheet. 

More Information

1. The calculator provides approximate estimations. There might be some insignificant gaps between calculated results and real values.

2. In some situations you may deal with an infrastructure of a mixed type, for example if you are planning to utilize hosts with 4 HBAs and 8 HBAs. To calculate the expected size of the databases, it is recommended to run calculation twice – once for each of the host types.

3. This calculator estimates the database size for Veeam ONE 9.5, including vSphere, Hyper-V and Veeam Backup & Replication infrasructures. 
 
Viewing all 4469 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>