Challenge
When installing the license file, the following error message may occur:License signature is invalid
↧
License cannot be installed in Veeam ONE 9.5
↧
Veeam Availability Console Migration FAQ
Challenge
This is a FAQ page for Veeam Managed Backup Portal (VMBP) to Veeam Availability Console (VAC) migrationCause
Answers to common questions can be found below.Solution
Can I upgrade Veeam Managed Backup Portal (VMBP) or VAC Beta to VAC GA?- No, we can migrate and install the product to a new VAC server but upgrading over an existing installation is not supported in the GA release.
What versions can be migrated?
- Currently the version requirement for migration is VMBP 1.0.0.295 or 2.0.0.317. Migrating from the VAC beta is not supported.
Can it be installed on the same server as VMBP?
- No, you must perform a clean installation of Veeam Availability Console. Do not configure the cloud infrastructure and do not connect the Veeam Cloud Connect server to Veeam Availability Console.
- Migration is server to server, not on a local install level.
- Do not uninstall VMBP until you complete the migration process. If VMBP is uninstalled, their will be no way to recover the configuration. A fresh setup of VAC will be required.
How do I install the migration tool and where is it located?
- Log on to the machine that runs Veeam Managed Backup Portal with a Local Administrator account. Make sure that the Local Administrator accounts on the VMBP and VAC servers have the following rights:
- Impersonate a client after authentication
- Allow log on locally
- Access this computer from the network
- Launch the VAC.MigrationTool setup file.
- Follow through the steps of the installation wizard.
- At the last step of the wizard, click Install.
- VAC Migration Tool installation will start.
- When the installation completes, click Finish to close the wizard.
More Information
Our official migration guide can be found here.↧
↧
Zlib decompression error: [-3] | Failed to decompress LZ4 block
Challenge
Backup or restore fails with either of the following errors:Error: Client error: Zlib decompression error: [-3].
OR
Error: Client error: Failed to decompress LZ4 block: Incorrect decompression result or length
Cause
Cyclic Redundancy Check (CRC) failed while extracting data from a backup file. This indicates that one or more blocks in that file are corrupted.Typically this error indicates hardware malfunction during storage or transmission of the backup file. Most types of storage are subject to a small degree of unrecoverable failure – this is commonly called Bit Rot.
Solution
If you are attempting restore and have multiple copies of the backup file, try using a different copy. If you have other restore points, try an older full backup or an incremental associated with an older full. If you are unable to recover the complete VM, file level recovery may still be possible.If the error is encountered during backup, try running an active full backup. This will bypass the need to read data from previous backup files.
The Windows event log on the repository server may contain Disk Event 7: “The device… has a bad block.” If so, run CHKDSK /F or /R. A small number of bad blocks are normal on most storage devices. If additional bad block events occur after running CHKDSK, check the SMART status and consider replacing the disk. If using a Network Attached Storage device, contact your storage vendor to determine what diagnostics are available.
More Information
Veeam Backup & Replication 6.5 added network traffic verification in order to detect corruption which might occur when sending data from a proxy to a repository or other proxy. Decompression errors in 6.5 and later are unlikely to be caused by a malfunctioning NIC, router, or other network device if the repository server is using a local disk. However, when backing up to a CIFS share, malfunctioning network hardware may be the cause of corrupted files.Synthetic full backups and reverse incremental backups both have the potential to copy data from corrupted backup files. Active full backups do not copy any data from existing backup files. Although it is best to perform periodic full-VM recovery tests, you can schedule monthly or quarterly active full backups to reduce the possibility that your latest backup contains corrupted data.
↧
Veeam licensing
Challenge
How is Veeam Backup & Replication licensed?
Solution
Veeam licensing for all products is described here: http://veeam.com/faq.html
You can verify your license key by logging in to www.veeam.com with your credentials: https://my.veeam.com/#/licenses/production. An updated key will be available for all customers with valid and active support contracts.
If you have difficulties retrieving your license file, go to My Account, and open a "Licensing" case to receive assistance from Veeam licensing.
To download Veeam products for trial license, go to https://www.veeam.com/downloads.html. The trial license key is sent to you in email after registering. The trial license is valid for 30 days from the moment of registration.
To obtain a full license key for the desired number of sockets, refer to http://www.veeam.com/buy-end-user.html. The full license includes a one-year maintenance plan.
More Information
To check check what version your license key is for, open the *.lic file in Notepad/Word and locate the section listed as "Version"For example if your "Version" is listed as 9.x you are able to install any patch for Veeam Backup and Replication 9.0 or Veeam Backup and Replication 9.5
↧
Health Service dropped data
Challenge
The following alerts can be seen in SCOM "Veeam Collector: Health Service dropped data" for agents located at the Veeam collector servers, additionally "Veeam Collector: Health Service workflows failed" alerts come to SCOM console.The settings of SCOM agent are correct (please see KB1026), clearing OpsMgr cache helps for a short amount of time.
The OperationsManager log on Veeam Collector machine shows events 4506, 1103 and 21405.
Cause
The issue is caused by unsupported decimal symbol setting under Veeam Collector service account.Solution
Steps to resolve the issue are:
1) Log in to Veeam Collector server under Veeam Collector service account
2) Open Control Panel -> Region and Language ->Additional Settings
3) Change Decimal symbol to "." (dot)
4) Restart Veeam VMware Collector service
5) Clear OpsMgr cache (please see KB1043)
More Information
If you have any questions or problems, please contact Veeam Support at https://my.veeam.com/#/open-case/step-1↧
↧
Health Service (Monitoring Host) Handle Count has exceeded the threshold
Challenge
The following alerts about handle counts are raised:
"Health Service (Monitoring Host) Handle Count has exceeded the threshold" or "Health Service Handle Count has exceeded the threshold" on collector server.
Cause
The monitors raising the mentioned alerts ensure that the "Process\Handle Count" counter for the "MonitoringHost.exe" and "HealthService.exe" processes does not exceed a specific threshold over a series of consecutive samples. If the conditions are met, this monitor will change to a critical state, which will then roll up to the "Health Service State" monitor.
In the Veeam MP case, the values that trigger the monitor may result from Collector server overload. If too many VMware hosts and VMs are monitored, then the Health Service may be overwhelmed when processing the data.
Current amount of handle counts can be checked using Windows Task Manager on the collector server:
1) Start Windows Task Manager and switch to the Processes tab
2) Choose View -> Select columns and enable Handles
After that you should be able to see a column named "Handles"
Solution
Please check configuration of SCOM Agent co-located with Veeam collector (see KB1026), make sure you don't have "Veeam Collector: Health Service dropped data" or "Veeam Collector: Health Service workflows failed" alerts raised (KB1765).If no additional alerts indicating performance issues with SCOM Agent occur, you can try increasing thresholds for 2 monitors based on current number of handles:
1) MonitoringHosts.exe "Veeam Collector: Health Service (Monitoring Host) Handle Count threshold"
2) HealthService.exe "Veeam Collector: Health Service Handle Count threshold"
Otherwise you may consider moving VMware monitoring jobs to other Veeam Collectors or co-locating Veeam Collector with a SCOM Management Server.
More Information
If you have any questions or problems, please contact Veeam Support at https://my.veeam.com/#/open-case/step-1↧
Downloading Veeam ONE Version 6.5
Challenge
You need to install Veeam One 6.5Solution
Veeam One 6.5 distribution can be downloaded here.Patch One for Veeam One 6.5 can be downloaded here.
The documentation pack for Veeam One 6.5 can be downloaded here.
More Information
If you have further questions or issues, open a case with Veeam Support at cp.veeam.com.↧
No VM names for Hyper-V in SCOM
Challenge
The Hyper-V topology is discovered correctly except for the Display Names of Virtual Machines, instead you can see only VM ID like in the screenshot below:Additionally, error events 3603 are logged in the OperationsManager event log on the Hyper-V server:
"VMDiscovery.js : 'vmid' is null or not an object error number: -2146823281"
Cause
The issue is caused by "ghost" roles for the affected VMs on the Failover Cluster Manager server or the VMM server. When our script discovers the VM names, it checks the VM list in the registry of the Cluster Manager or the VMM server at HKEY_LOCAL_MACHINE\Cluster\ResourcesThe behavior may manifest itself if a VM has been manually removed from inventory. By design, Hyper-V should be updating the registry appropriately. If this does not happen, the "ghost" VM has no VmID under "Parameters". Here are two examples of invalid configuration:
[HKEY_LOCAL_MACHINE\Cluster\Resources\8ad1692b-3d65-4716-8517-e8092c469af4]
"Name"="Name of VM Configuration"
"Type"="Virtual Machine Configuration"
"SeparateMonitor"=dword:00000000
[HKEY_LOCAL_MACHINE\Cluster\Resources\8ad1692b-3d65-4716-8517-e8092c469af4\Parameters]
"DependsOnSharedVolumes"=hex(7):61,00,62,00,63,00,33,00,36,00,33,00,32,00,63,\
00,2d,00,37,00,36,00,36,00,66,00,2d,00,34,00,38,00,61,00,62,00,2d,00,39,00,\
36,00,61,00,36,00,2d,00,37,00,35,00,62,00,61,00,63,00,65,00,63,00,65,00,34,\
00,63,00,32,00,38,00,00,00,00,00
or
[HKEY_LOCAL_MACHINE\Cluster\Resources\e27f0edb-66c2-4be0-a1c9-3a8545e6e15f]
"Name"="Name of VM"
"Type"="Virtual Machine"
"SeparateMonitor"=dword:00000000
[HKEY_LOCAL_MACHINE\Cluster\Resources\e27f0edb-66c2-4be0-a1c9-3a8545e6e15f\Parameters]
Solution
The workaround is to remove the Virtual Machines with missing VmID from the registry of the Failover Cluster Manager or the VMM server.More Information
There is a side effect to the suggested workaround: the failover will no longer work for the VMs that have been removed from registry.If you have any questions, please, contact Veeam Support.
↧
Uninstalling Veeam Collectors if a System Resource Pool Was Used for Auto-Deployment
Challenge
If during auto-deployment of Veeam Collectors one of the system resource pools was used (All Management Servers Resource Pool, Notifications Resource Pool or AD Assignment Resource Pool), you will need to use the workaround described below to remove all collectors automatically.Cause
Uninstallation of all collectors is required.Solution
Log on to Veeam Extensions Server (VES) and run regedit. Locate the following key:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Virtualization Extensions for VMware\Manager
and set the value ResourcePool to a blank value. This will trigger uninstallation of all collectors, which can take up to 8 hours depending on the size of your infrastructure. To speed it up, you can restart HealthService on the VES Server.
More Information
If you have any questions, please, contact Veeam Support.↧
↧
CIM Patch for Veeam MP v.7
Challenge
After upgrading to v.7, an unreasonable number of the following alerts are visible in SCOM:"Veeam VMware Collector: Failed to gather Host hardware data via CIM"
Cause
To optimize CIM collection, asynchronous polling method was introduced in Veeam MP 7. If in response to Veeam query only part of the requested sensor information is returned, a retry is initiated, and Refresh Hardware method cannot be called.Solution
Fix can be downloaded here. It should be applied on all collectors.More Information
If the errors persist after applying the patch, please refer to the following KB article. If you have any questions, please contact Veeam Support.↧
Jobs fail with “Error: Invalid product version” after upgrade to Veeam Backup & Replication v9
Challenge
After upgrading to Veeam Backup & Replication v9, all jobs fail with “Error: Invalid product version."Cause
During the upgrade process the new v9 license file was not installed.Solution
Install the new v9 license file that can be acquired from the support portal.The following link will take you directly to your accounts production keys.
https://my.veeam.com/#/licenses/production
For information on how to install the new license, please review:
http://helpcenter.veeam.com/backup/vsphere/install_license.html
↧
Backup Copy cancels with message: ‘Restore point is located in backup file with different block size’
Challenge
A Backup Copy job terminates with the message: ‘Restore point is located in backup file with different block size’ after adding new files or linked jobs.Cause
Veeam Backup & Replication does not copy restore points if the block size of the restore point on the source backup repository differs from the block size of restore points on the target backup repository.The data block size for restore points on the target backup repository is set at the first synchronization cycle of the backup copy job. This size is taken from the corresponding settings of the primary backup job — the backup job that creates the backup chain on the source backup repository.
If after the first synchronization cycle you add to the backup copy job new sources that use a different data block size, Veeam Backup & Replication will detect such restore points and display the “Restore point is located in backup file with different block sizе” message.
Solution
Version 7.x: A Backup Copy job terminates with the message: ‘Restore point is located in backup file with different block size’ after adding new files or linked jobs.Version 8.0.0.807- 8.0.0.917: The Job MAY finish with a 1-time Warning;
“Source backup file has different block size. Expected block size: X, actual: ([backup name: Backup: ChangeBlockSizeToBCJ, block size: Y])”
After the above warning or without warning, Job does not process anything and eventually fails with:
“No up-to-date restore points available”
If the job worked previously and is now failing please review the following:
Version 9.x: The backup copy job can be run with a new active full to start a new chain in the backup copy job with the correct block size.
Older solutions below:
Step 1:
The first troubleshooting step is to change the storage optimization setting within the source backup job back to its original setting and force the source job to create a new active full. Then attempt to “sync now” with the backup copy job. If the backup copy job still fails after performing this step, proceed to step 2.
Note: If changing the storage optimization setting back to its previous value is not an option proceed to step 2.
Step 2:
If changing the storage optimization back to its previous value is not an option or it did not correct the issue, you will need to start a new backup set for the backup copy job. http://www.veeam.com/kb1885
If you are attempting to seed a new backup copy job or running a backup copy job for the first time and receiving this error please review the following:
Step 1:
Create a new backup set with the source backup job. http://www.veeam.com/kb1885
If seeding the Backup Copy job, use the new backup set to seed. If not seeding please create a new Backup Copy job.
More Information
http://helpcenter.veeam.com/backup/70/vsphere/backup_copy_select_point.html↧
Backup Copy Seeding and Mapping for Cloud Connect
Challenge
Details how to seed a backup copy job with cloud providersSolution
The steps differ slightly from regular backup copy seeding. Please contact your provider for their preferred method of receiving seed data. The provider may have their own process for you to use. This KB details how to create a backup copy seed within the software with instructions specific for Cloud Connect, however the provider chooses to receive the data.Tenant must perform these steps first
1. Create a new, auxiliary, backup copy job. Add VMs whose restore points you want to copy to the auxiliary backup copy job. Target the auxiliary backup copy job to some backup repository on the source side that is not the source backup repository location in the GUI. You are unable to target ‘Backup Repository’ for both Backup and Backup Copy jobs. This backup repository will be used as an intermediate one.
If the Cloud Repository is a SOBR then the new backup copy job will have the stipulations listed below. (Please note this process is different than migrating to a SOBR as described in https://www.veeam.com/kb2236 and migration still requires contacting Veeam support for assistance)
If the Cloud Repository is a SOBR then the new backup copy job will have the stipulations listed below. (Please note this process is different than migrating to a SOBR as described in https://www.veeam.com/kb2236 and migration still requires contacting Veeam support for assistance)
A. If the SOBR is using per-VM then the Backup Copy Job creating the seed should also use per-VM.
B. There should not be any spaces in the Backup Copy Job name. (any spaces needed can be substituted with an underscore "_")
B. There should not be any spaces in the Backup Copy Job name. (any spaces needed can be substituted with an underscore "_")
2. Run the auxiliary backup copy job to create a full backup file (VBK with VBM metadata file) in the intermediate backup repository, then disable the Backup Copy job.
3. Perform a ‘Remove from configuration’ on the backup set under Backups > Disk (Copy)
4. Contact your provider for the preferred method of receiving data.
Note: Contact your provider for the preferred method of receiving data.
Provider must then perform these steps second
1. Upon receiving the tenant’s backup seed data (VBK with VBM metadata file), move these to the tenant’s backup directory. Example: E:\Backups\TenantName\JobName\File.VBM
If the Cloud Repository is a SOBR then the requirements listed below must be met. (Please note this process is different than migrating to a SOBR as described in https://www.veeam.com/kb2236 and migration still requires contacting Veeam support for assistance)
If the Cloud Repository is a SOBR then the requirements listed below must be met. (Please note this process is different than migrating to a SOBR as described in https://www.veeam.com/kb2236 and migration still requires contacting Veeam support for assistance)
A. The VBM file must be moved to each of the extents when seeding.
B. Performance SOBRs must have the VBK and VIB files on different extents.
B. Performance SOBRs must have the VBK and VIB files on different extents.
2. Inform the tenant that data has been transferred to their repository location.
Tenant must then perform these steps last
1. Rescan the cloud repository. Backup files should then appear under Backups > Cloud
Note: If the original backup copy files were encrypted, you will need to input the password for the backup copy set under Backups > Encrypted before moving forward.
2. Edit the original backup copy job to change the repository to the Cloud Repository.
3. Click ‘Map Backup’ and select the Backup Copy chain that is imported.
4. Enable the Backup Copy job, right click the job, and select ‘Sync Now’.
3. Click ‘Map Backup’ and select the Backup Copy chain that is imported.
4. Enable the Backup Copy job, right click the job, and select ‘Sync Now’.
More Information
https://helpcenter.veeam.com/docs/backup/vsphere/backup_copy_mapping_auxiliary.html?ver=95↧
↧
Release Notes for Veeam Backup & Replication 9.5 Update 2
Challenge
Release Notes for Veeam Backup & Replication 9.5 Update 2Cause
Please confirm you are running version 9.5.0.580, 9.5.0.711, 9.5.0.802 or 9.5.0.823 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console. After upgrading, your build will be version 9.5.0.1038.If you use Veeam ONE to monitor Veeam Cloud Connect, make sure you install this update. You will need to install the update for Veeam ONE first, then install update 9.5.0.1038 for Veeam Backup & Replication.
Solution
As a result of on-going R&D effort and in response to customer feedback, Update 2 includes hundreds of enhancements and bug fixes, the most significant of which are listed below.Platform support
- Cisco HyperFlex Systems (formerly HX-Series/SpringPath) support for Backup from Storage Snapshots functionality.
- HPE 3PAR StoreServ 3.3.1 support and improved scalability by migrating some API calls from SSH to RESTful API.
- Microsoft Hyper-V BigEndian platform support.
- Microsoft Exchange 2016 CU5 support for mailbox item recovery with Veeam Explorer for Microsoft Exchange.
- NetApp ONTAP versions from 8.1 up to 9.2 support.
- Oracle 12.2 support for all Oracle database backup and restore functionality.
- Veeam Agent for Linux 1.0 Update 1 (build 1.0.1.364) support, including new 1-Click FLR via Veeam Backup Enterprise Manager.
- Veeam Agent for Microsoft Windows 2.0 (build 2.0.0.700) support, including application-item recovery support from agent backups.
- VMware vCloud Director 8.20 support.
- VMware vSAN 6.6 support.
- Restore to original location. If the original VM cannot be found by moRef identifier (as is the case if it was deleted and then restored from backup), the Multi-OS File Level Recovery wizard will prompt the user to specify target VM manually instead of failing.
- Failback performance improvements. Failback can now optionally use changed block tracking data to determine the changes between the original VM and replica VM state. This dramatically accelerates the failback performance due removing the need to read the entire original VM disks (“Calculating original signature” operation). For VMware hypervisor, we recommend that this option is not used if the failover event was triggered by a disaster that involved host or storage crash or dirty shutdown, as CBT data may be inconsistent in this Case.
- Optional NFS exports creation. You can now prevent Veeam from automatically creating the required NFS export rules on the NetApp storage by clearing the “Create required NFS export rules automatically” in the New NetApp Storage wizard.
- Performance improvements. The performance of Backup from Storage Snapshot with application-aware processing enabled has been noticeably improved.
- LTO7 path failover support. Added support for LTO7 tape libraries with path failover functionality enabled.
- Exclusive drivers support. Added support for exclusive tape library drivers (on top of already supported non-exclusive drivers).
- VeeamZIP usability improvements. VeeamZIP menu item with the default location will not be shown until a user performs VeeamZIP for the first time, selecting the required destination during this process. After that, said menu item will appear, reflecting the previously selected location. This should prevent users from accidentally overfilling the default C:\Backup VeeamZIP location.
- ExaGrid preset. Changed the default concurrent tasks value from 1 to 10 per vendor's request.
- Start-VBRZip enhancements. Added NetworkCredentials parameter to Start-VBRZip cmdlet to enable automating backups to file shares.
- Backup import enhancements. Added support for importing backups from DELL EMC Data Domain and HPE StoreOnce repositories.
- Components auto-update. Update setup now offers an option to initiate the upgrade of all remote Veeam component automatically. This covers all Veeam components except Network Extension Appliances (part of Veeam Cloud Connect Replication functionality)
- Update performance. The number of concurrently updated remote components have been increased to 10 to reduce large backup environments update time, especially with high latency networks. This value can be further increased by creating MaxConcurrentComponentUpgrades (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server.
- Streamlined updates. Installing the update no longer requires to disabling all jobs and stopping Veeam services manually. However, you still have to ensure there’s no running backup or restore jobs before installing the update.
- Update 2 introduces Veeam Backup Remote Access functionality, scalability and reporting enhancements for Veeam Cloud Connect platform, and improved offline usage reporting. For the full list of service provider specific enhancements and bug fixes, please refer to the issue tracking topic in the private VCSP forum. If you are VCSP but don't have access, please apply to Cloud & Service Providers group using Veeam forum's User Control Panel.
- Networkless restores for files above 10MB should no longer result in corrupted file restored.
- Backup infrastructure resource scheduling algorithms have been improved to reduce job initialization delays in large infrastructures.
- Shutting down or rebooting the backup server should now correctly stop all jobs.
- Repository throttling rules should now correctly apply to Veeam Agent for Windows 2.0 synthetic full backups.
- Instant VM Recovery should now be possible for VMs for which the original host is no longer registered with Veeam.
- Fixed backup metadata resync issues caused by using storage-based replication or similar means of transferring backup files between Veeam backup repositories registered in the same backup server.
- Improved SureBackup performance and domain controller (DC) recoverability testing logic. As a side effect, the recoverability testing for DCs backed up without application-aware processing will always fail (which however represents typical real-life recovery result from such a backup).
- Improved Hyper-V 2016 RCT backup performance and off-host backup reliability.
- Improved Direct NFS transport mode compatibility with Tintri storage.
More Information
[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/kb2283/]]
Note: Performing a reboot of the Veeam Server after update deployment is necessary to finalize the update.
MD5 checksum for veeam_backup_9.5.0.1038.update2_setup.exe: 3c4f6a6162b382c13489ab37e6b03fed
If you use Veeam ONE to monitor Veeam Cloud Connect, make sure you install this update. You will need to install the update for Veeam ONE first, then install update 9.5.0.1038 for Veeam Backup & Replication.
↧
Creating a VMware ESXi extension (VIB) for Veeam Backup from Storage Snapshot with Cisco HyperFlex IOvisor processing
Challenge
This article contains instructions on how to create a VMware ESXi extension (VIB) for Veeams Backup from Storage Snapshot with Cisco HyperFlex IOvisor processing.To achieve the optimal balancing within the Cisco HyperFlex data network at Backup from Storage Snapshot processing over NFS, it is needed to change the ESXi host firewalls. See more background information here.
One of the Methods to change the ESXi host firewall is by a newly created VIB file that can be created with help of the VMware VIB Author Software.
Please follow the next steps to create the VIB.
Solution
Create a VIB in SLES11SLES11 can be downloaded here.
VMware VIB Author can be downloaded here.
All steps are performed as the root user from the root (/) directory.
1. Prepare SLES
zypper install python-lxml zypper install python-urlgrabber
2. Install VIB Author
cd /tmp rpm -ivh vmware-esx-vib-author-5.0.0-0.0.847598.i386.rpm cd /
3. Create File Directory
mkdir stage mkdir stage/payloads mkdir stage/payloads/payload1 mkdir stage/payloads/payload1/etc mkdir stage/payloads/payload1/etc/vmware mkdir stage/payloads/payload1/etc/vmware/firewall
4. Copy the required files to the folder tree
The "descriptor.xml" (link here) must be copied to /stage
descriptor.xml sample:
<vib version="5.0">
<type>bootbank</type>
<name>VeeamCiscoHXFirewall</name>
<version>1.0.0-0.0.1</version>
<vendor>Veeam</vendor>
<summary>Veeam Firewall rule for Cisco HyperFlex</summary>
<description>Adds inbound ports required by Veeam</description>
<relationships>
<depends></depends>
<conflicts/>
<replaces/>
<provides/>
<compatibleWith/>
</relationships>
<software-tags>
</software-tags>
<system-requires>
<maintenance-mode>false</maintenance-mode>
</system-requires>
<file-list>
<file></file>
</file-list>
<acceptance-level>community</acceptance-level>
<live-install-allowed>true</live-install-allowed>
<live-remove-allowed>true</live-remove-allowed>
<cimom-restart>false</cimom-restart>
<stateless-ready>true</stateless-ready>
<overlay>false</overlay>
<payloads>
<payload name="payload1" type="vgz"></payload>
</payloads>
</vib>
The “VeeamCiscoHXFirewall.xml” <download link> must be copied to /stage/payloads/payload1/etc/vmware/firewall
The VeeamCiscoHXFirewall.xml for Cisco HX version < 2.5:
<ConfigRoot>
<service id='9230'>
<id>VeeamCiscoHXFirewall</id>
<rule id='0000'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>
<begin>0</begin>
<end>65535</end>
</port>
</rule>
<enabled>true</enabled>
<required>false</required>
</service>
</ConfigRoot>
The VeeamCiscoHXFirewall.xml for Cisco HX version >= 2.5:
<ConfigRoot>
<service id='9230'>
<id>VeeamCiscoHXFirewall</id>
<rule id='0000'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>111</port>
</rule>
<rule id='0001'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>2049</port>
</rule>
<rule id='0002'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>2449</port>
</rule>
<enabled>true</enabled>
<required>false</required>
</service>
</ConfigRoot>
5. Create the VIB using vibauthor:
vibauthor -C -t stage -v VeeamCiscoHXFirewall -f
6. Creation finished, ready for download
The VIB is now created and available in the root (/) directory. You can use the SCP client to download the VIB to your local operating system.
7. Install on ESXi
Install the Firewall VIB on ESXi:
Repeat the following steps on all Cisco HyperFlex nodes in your cluster.
a. Enable ssh and log in to your ESXi host using a ssh tool like PuTTY
b. Copy the VIB file to the ESXi host's tmp folder using HTTP or a SCP client
c. Install the VIB
Command:
esxcli software vib install -v /tmp/VeeamCiscoHXFirewall.vib -f
d. Verify that the VIB was installed
Command:
esxcli software vib list | grep 'Veeam'
e. Verify that the new firewall rule is active
Command:
esxcli network firewall ruleset list
Note: If the VIB installation fails, you may need to set the acceptance level to CommunitySupport and retry the installation.
Command:
esxcli software acceptance set --level=CommunitySupported
Set the Veeam Proxy Servers
1. Enable allowed IP list for the new firewall rule
Command:
esxcli network firewall ruleset set -r "VeeamCiscoHXFirewall" -a false
2. Set the Veeam proxy server data network IP that is on the Hyperflex "Storage Controller Data Network"
Repeat the following command for each Veeam proxy server:
esxcli network firewall ruleset allowedip add -r "VeeamCiscoHXFirewall" -i "172.16.3.10"
3. Verify that the IPs are set
Command:
esxcli network firewall ruleset allowedip list | grep -v "All"
Note: Veeam recommends to set the IPs of each Veeam proxy server that is on the HyperFlex “Storage Controller Data Network” in the firewall rule. Otherwise the firewall rule is enabled for all incoming connections. Issue this command once per IP Address. It is important to use the IP Address on the “Storage Controller Data Network”, and not the public, or management IP address.
Check if everything is configured correctly
1. Check the Security Profile on the ESXi hosts
2. Check the VIB
esxcli software vib list | grep 'Veeam'
3. Check the ruleset
esxcli network firewall ruleset list
4. Check which Veeam Proxy IPs are assigned
esxcli network firewall ruleset allowedip list | grep -v "All"
↧
Manual Firewall changes for Veeam Backup from Storage Snapshot with Cisco HyperFlex IOvisor processing
Challenge
This article describes making manual firewall changes for Veeam Backup from Storage Snapshot with Cisco HyperFlex IOvisor processingSolution
To achieve the optimal balancing within the Cisco HyperFlex data network at Backup from Storage Snapshot processing, it is needed to change the ESXi host firewall. See more background information here.One of the methods to change the ESXi host firewall is by manual creation of an ESXi host firewall rule. This configuration is reset by an ESXi host reboot and can be used for test environments.
To open ports on ESX(i) hosts for Cisco HX < 2.5, add the following firewall rule to the services.xml file on an ESX(i) host.
<!--Cisco Firewall configuration information -->
<ConfigRoot>
<service id='9230'>
<id>VeeamCiscoFirewall</id>
<rule id='0000'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>
<begin>0</begin>
<end>65535</end>
</port>
</rule>
</service>
</ConfigRoot>
To open ports on ESX(i) hosts for Cisco HX >= 2.5, add the following firewall rule to the services.xml file on an ESX(i) host.
<!--Cisco Firewall configuration information -->
<ConfigRoot>
<service id='9230'>
<id>VeeamCiscoHXFirewall</id>
<rule id='0000'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>111</port>
</rule>
<rule id='0001'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>2049</port>
</rule>
<rule id='0002'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>2449</port>
</rule>
<enabled>true</enabled>
<required>false</required>
</service>
</ConfigRoot>
The following example shows all steps required to open the firewall at an ESXi host SSH connection:
1. Back up the current services.xml file by running the command:
cp /etc/vmware/firewall/service.xml /etc/vmware/firewall/service.xml.bak
2. Modify the access permissions of the service.xml file to allow writes by running the chmod command:
chmod 644 /etc/vmware/firewall/service.xml chmod +t /etc/vmware/firewall/service.xml3. Open the service.xml file in a text editor:
vi /etc/vmware/firewall/service.xml4. Add the rule to the service.xml file (see example above)
5. Revert the access permissions of the service.xml file to the read-only default by running the command:
chmod 444 /etc/vmware/firewall/service.xml6. Refresh the firewall rules for the changes to take effect by running the command:
esxcli network firewall refresh7. Enable the new firewall rule:
esxcli network firewall ruleset set -r "VeeamCiscoFirewall" -e true -a false8. Bind the firewall rule to all Veeam proxy server data network IPs. This is the IP on the HyperFlex “Storage Controller Data Network”. Repeat the command for each proxy server:
esxcli network firewall ruleset allowedip add -r "VeeamCiscoFirewall" -i "<yourVeeamProxyIP>"9. Check the IP binding
esxcli network firewall ruleset allowedip list | grep -v "All"10. Check if the firewall rule is enabled
esxcli network firewall ruleset list
More Information
For more information about custom firewall rule creation, click here.↧
Usage of a predefined VMware ESXi extension (VIB) for Veeams Backup from Storage Snapshot with Cisco HyperFlex IOvisor processing
Challenge
This article describes the usage of a predefined VMware ESXi extension (VIB) for Veeams Backup from Storage Snapshot with Cisco HyperFlex IOvisor processing.Cause
To achieve optimal balancing within the Cisco HyperFlex data network at Backup from Storage Snapshot processing, it is needed to change the ESXi host firewall.See more background information here.
One of the Methods to change the ESXi host firewall is by a pre-defined VIB that can be found at the Veeam Community GitHUB site.
To implement this, follow the below instructions.
Solution
Install the Firewall VIB on ESXi:Repeat the following steps on all Cisco HyperFlex nodes in your cluster.
1. Enable ssh and log in to your ESXi host by using a tool like PuTTY
2. Copy the VIB file to the ESXi host's tmp folder using HTTP or a SCP client
3. Install the VIB
Command:
esxcli software vib install -v /tmp/VeeamCiscoHXFirewall.vib -f
4. Verify the VIB was installed
Command:
esxcli software vib list | grep 'Veeam'
5. Verify the new firewall rule is active
Command:
esxcli network firewall ruleset listNote: If the VIB installation fails, you might need to set the acceptance level to CommunitySupport and retry the installation.
Command:
esxcli software acceptance set --level=CommunitySupported
Set the Veeam Proxy Servers
1. Enable allowed IP list for the new firewall rule
Command:
esxcli network firewall ruleset set -r "VeeamCiscoHXFirewall" -a false
2. Set the Veeam proxy server data network IP that is on the Hyperflex ("Storage Controller Data Network")
Repeat the following command for all Veeam proxy server or set a subnet:
esxcli network firewall ruleset allowedip add -r "VeeamCiscoHXFirewall" -i "172.17.53.53."
3. Verify the IPs are set
Command:
esxcli network firewall ruleset allowedip list | grep -v "All"
Note: Veeam recommends to set the all IPs of Veeam proxy servers in the firewall rule. Otherwise the firewall rule is enabled for all incoming connections. You can specify either the IP address or a subnet. Use one command per proxy.
Check if everything is configured correctly
1. Check the Security Profile on the ESXi hosts
For HX systems < HX2.5 using the relevant VIB.
For HX system >= HX2.5 using the relevant VIB.
2. Check the VIB
Command:
esxcli software vib list | grep 'Veeam'
3. Check the ruleset
Command:
esxcli network firewall ruleset list
4. Check which Veeam Proxy IPs are assigned
Command:
esxcli network firewall ruleset allowedip list | grep -v "All"
↧
↧
HCL-Scality-RING
Challenge
Product Information:
Product Family: Scality RING
Status: Veeam Ready - Archive
Classification Description: Verified disk archive storage that can be used as a Backup Copy target. Synthetic full backups, granular restores, and vPower features may not provide sufficient performance or be supported.
Solution
Product Details:
Model number: Scality RING
Number of Drives: 48 SATA, 6 SSD per node (6 nodes)
Drive type: SATA and SSD
Firmware version: RING Software Version 5.1.7
Additional support: Configurations with 6 or more nodes with at least 48 SATA drives and 6 SSD’s per node
General product family overview: The Scality RING is software that turns any standard x86 servers into web-scale storage. With the RING, you can store any amount of data, of any type, with incredible efficiency and 100% reliability, guaranteed—all while reducing costs by as much as 90% over legacy systems.
Veeam Details:
- Repository Type: Shared folder
- Align backup file data blocks: No
- Decompress backup data blocks before storing: No
- Use per-VM backup files: Yes (optional)
- Enable In-Line Data Deduplication: Yes
- Compression level: Optimal
- Storage Optimization: Local Target (16TB+ backup files) (Settings for source backups only, it guarantees better performance on this storage due to a bigger block size in backup copy)
More Information
Company Information:
Company name: Scality
Company overview: Scality, the world leader in object and cloud storage, bridges the gap between application vendors and industry standard hardware providers to meet your cost-effective storage scale, durability, cloud and performance requirements.
↧
Usage of a predefined VMware ESXi extension (VIB) for Veeams Backup from Storage Snapshot with Cisco HyperFlex IOvisor processing
Challenge
This article describes the usage of a predefined VMware ESXi extension (VIB) for Veeams Backup from Storage Snapshot with Cisco HyperFlex IOvisor processing.Cause
To achieve optimal balancing within the Cisco HyperFlex data network at Backup from Storage Snapshot processing, it is needed to change the ESXi host firewall.See more background information here.
One of the Methods to change the ESXi host firewall is by a pre-defined VIB that can be found at the Veeam Community GitHUB site.
To implement this, follow the below instructions.
Solution
Install the Firewall VIB on ESXi:Repeat the following steps on all Cisco HyperFlex nodes in your cluster.
1. Enable ssh and log in to your ESXi host by using a tool like PuTTY
2. Copy the VIB file to the ESXi host's tmp folder using HTTP or a SCP client
3. Install the VIB
Command:
esxcli software vib install -v /tmp/VeeamCiscoHXFirewall.vib -f
4. Verify the VIB was installed
Command:
esxcli software vib list | grep 'Veeam'
5. Verify the new firewall rule is active
Command:
esxcli network firewall ruleset listNote: If the VIB installation fails, you might need to set the acceptance level to CommunitySupport and retry the installation.
Command:
esxcli software acceptance set --level=CommunitySupported
Set the Veeam Proxy Servers
1. Enable allowed IP list for the new firewall rule
Command:
esxcli network firewall ruleset set -r "VeeamCiscoHXFirewall" -a false
2. Set the Veeam proxy server data network IP that is on the Hyperflex ("Storage Controller Data Network")
Repeat the following command for all Veeam proxy server or set a subnet:
esxcli network firewall ruleset allowedip add -r "VeeamCiscoHXFirewall" -i "172.17.53.53."
3. Verify the IPs are set
Command:
esxcli network firewall ruleset allowedip list | grep -v "All"
Note: Veeam recommends to set the all IPs of Veeam proxy servers in the firewall rule. Otherwise the firewall rule is enabled for all incoming connections. You can specify either the IP address or a subnet. Use one command per proxy.
Check if everything is configured correctly
1. Check the Security Profile on the ESXi hosts
For HX systems < HX2.5 using the relevant VIB.
For HX system >= HX2.5 using the relevant VIB.
2. Check the VIB
Command:
esxcli software vib list | grep 'Veeam'
3. Check the ruleset
Command:
esxcli network firewall ruleset list
4. Check which Veeam Proxy IPs are assigned
Command:
esxcli network firewall ruleset allowedip list | grep -v "All"
↧
Veeam Backup & Replication Upgrade Paths
Challenge
This article documents the path to be taken to get to the most recent version.Solution
Important Note Regarding PerformanceVeeam Backup & Replication provides an option during installation to create a local SQL Express instance. This option is often taken and as such older versions of Veeam that are then updated may be running on old SQL Express instances. This can affect performance. It may be advised to upgrade the local SQL instance to the most current supported version after first upgrading Veeam to the latest version and update. All versions of Veeam Backup & Replication after 8.0.0.917 (Patch 1) support SQL 2014.
Note: Versions 9.0 and higher require a 64 bit OS for installation.
Please refer to the following links for steps and more information on upgrading to 9.0 or 9.5:
Upgrade to 9.0: https://helpcenter.veeam.com/backup/vsphere/upgrade_vbr.html
Upgrade to 9.5: https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr.html?ver=95
9.5 Update 2: https://www.veeam.com/kb2283
7.0.0.x
7.0.0.871 -> 9.0.0.x -> 9.5.0.x
To upgrade from 7.0 to 9.0, you must have 7.0 Patch 4 installed (7.0.0.871).
Link to 7.0 Patch 4: https://www.veeam.com/kb1891
Refer to above links for steps to upgrade.
8.0.0.x
8.0.0.x -> 9.0.0.x -> 9.5.0.x
8.0.0.2084 -> 9.5.0.x
To upgrade from 8.0 to 9.5, you must have 8.0 Update 3 installed (8.0.0.2084).
Link to 8.0 Update 3: https://www.veeam.com/kb2068
Refer to above links for steps to upgrade.
9.0.0.x
9.0.0.x -> 9.5.0.x
Any version of 9.0.0.x can upgrade directly to 9.5.
Refer to the above links for steps to upgrade.
More Information
Veeam Version 9.0 Supported Versions:vSphere Supported Versions: 4.1, 5.x, 6.0
Hyper-V Supported Versions: 2008 R2 SP1, 2012, 2012 R2
Veeam Database SQL Versions: SQL 2005, 2008, 2008 R2, 2012, 2014
Veeam Version 9.5 Supported Versions:
vSphere Supported Versions: 4.1, 5.x, 6.x (6.5 Supported with 9.5 Update 1 – 9.5.0.823)
Hyper-V Supported Versions: 2008 R2 SP1, 2012, 2012 R2, 2016, Nano
Veeam Database SQL Versions: SQL 2008, 2008 R2, 2012, 2014, 2016
↧