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

Uninstalling Veeam Collectors if a System Resource Pool Was Used for Auto-Deployment

$
0
0

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

$
0
0

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.

Maximum, minimum, average and latest CPU Usage values differ in VMware vCenter and Veeam Monitor

$
0
0

Challenge

The values in the VMware CPU Usage performance graphs and table values are twice as high as those of the Veeam Monitor graphs.

VMware vSphere example:

User-added image

Veeam Monitor example:
User-added image

Cause

VMware calculates these values with Hyperthreading Technology enabled.

The VMware vSphere client shows that “Hyperthreading” is in the “Active” state under the “General” section on the Summary tab for the ESX(i) host within the virtual infrastructure:

User-added image

As a result, the “Advanced” performance page for this host shows total values for all processors but with the Hyperthreading feature enabled 

Once all object are selected under the Chart Option window, the CPU Usage is displayed for all virtual CPUs and the ESX(i) host itself. Summing up the average values of each virtual CPU and then dividing by the number of virtual CPUs produces a value approximately two times smaller than the TOTAL CPU Usage value for the host.

Veeam Monitor calculates the total CPU Usage without using VMware’s “Total CPU Usage for entire host with Hyperthreading enabled” option. It takes each CPU's Usage and then performs calculations as described above. Thus, in Veeam Monitor, the Total CPU Usage value is two times smaller than CPU Usage for the entire host on VMware’s graphs.

Solution

No solution required as this is the expected behavior.

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support

Veeam ONE installation fails with "Couldn't create crypto provider" message

$
0
0

Challenge

Veeam ONE installation fails with "Couldn't create crypto provider" message.

Cause

One of the known issues with Microsoft update 3000850 as per this MS KB article is the following: Opening Credential Manager fails with error 0x80090345", that also affects creating the crypto provider.

Solution

Follow these steps:

    1. On the Veeam ONE Server: Click Start > Run, type regedit, and then click OK.
    2. Navigate to the following path: HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb.
    3. Create a new DWORD (32-bit value) and name it ProtectionPolicy.
    4. Set the value to 1 and save the changes.
    5. Restart the computer.

If the above-mentioned solution does not help, please follow the next Microsoft article.

More Information

If you have any questions, contact Veeam Support.

Veeam ONE Monitor Client Cannot Connect to Veeam ONE Monitor Server

$
0
0

Challenge

Veeam ONE Monitor Client cannot connect to Veeam ONE Monitor Server. The following error occurs when you open the Veeam ONE Monitor console:
 
User-added image

Cause

Under certain circumstances, Veeam ONE Monitor Client cannot establish connection with Veeam ONE Monitor Server.

Solution

First of all, make sure Veeam ONE Monitor Server service is up and running.

In case the service is running properly, confirm the following:

1. The name of the Veeam ONE Monitor Server is correctly specified in Veeam ONE Monitor client settings.
2. The Veeam ONE Monitor Server is reachable from the machine where Veeam ONE Monitor Client runs.
3. In multi-Monitor Client environment, connection to Veeam ONE Monitor Server may fail with one of the following errors:
 
Service connection failed Address = \\IP_Address\pipe\VeeaMDCS Error = 0xe7
Service connection failed Address = \\IP_Address\pipe\VeeaMDCS Error = 0x5

To resolve this issue, add the Veeam ONE Monitor Server service account to the Veeam ONE Administrators security group.
 
4. The ports used by Veeam ONE Monitor Client to connect to the Server have to be opened:
TCP/139
TCP/445
UDP/137

Besides these standard ports, Veeam ONE Client also uses dynamic TCP ports 49152 - 65535. Check if the mentioned ports range is open on the firewall.

NOTE: For versions 6.x-7.x of Veeam ONE, the account that is used to run Veeam ONE Monitor Client must be included in the Veeam ONE Users security group on the Veeam ONE Server.

More Information

If you have any questions or problems, please contact Veeam Support.

VeeamONE Update Failing – The specified path, file name, or both are too long.

$
0
0

Challenge

VeeamONE V9.5 Update # 1 install fails with the following error: “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 Characters, and the directory name must be less than 248 characters.”

Cause

Conflict with BusinessView component installation directory

Solution

1. Remove existing Veeam ONE Business view component from the server manually using VeeamONE installation ISO:
2. Open ISO in File Explorer -> go to “BusinessView” folder -> run “BV_x64.msi” and remove Business View component.
3. Run the same file again and perform a clean Business View installation (specify the same database during the installation);
4. Install the most recent Update.

Unexpected Highest Latency Values Shown in Veeam One

$
0
0

Challenge

Veeam One indicates unreasonably high values for highest latency on VMs (see screenshot below):

User-added image

Cause

The same latency values can be observed in VI Client performance charts under disk/real-time during snapshot deletion. The values may also be negative.
User-added image

User-added image
 

Solution

This is a known behavior of VMware. KB 2001676 by VMware describes the behavior in more detail.

False alerting on Veeam side will be eliminated in the coming patch for Veeam One.

 

More Information

Customers facing this issue are advised to contact VMware Support for assistance.

Release Notes for Veeam ONE 9.5 Update 3

$
0
0

Challenge

Release Notes for Veeam ONE 9.5 Update 3

Cause

Please confirm you are running Veeam ONE 9.5 prior to installing this update. You can check this under Help | About in Veeam ONE Monitor Client, the build number should be 9.5.0.xxx. After upgrading, your version build will be 9.5.0.3801.

This update should be applied to the Veeam ONE server, as well as remote systems with the Veeam ONE Monitor Client.

Before you apply the update, make sure you have a full backup of Veeam ONE database.

Solution

New Features and Enhancements


General
 
  • Veeam Agents Backup Monitoring and Reporting. Monitoring and reporting for Veeam Agent for Windows and Veeam Agent for Linux
  • Location Tag Support. Veeam ONE pre-defined reports and Monitor UI now support location tags for VMs, hosts, computers configured in Veeam Backup & Replication to observe data sovereignty.  
  • Microsoft SQL Server 2017 Support. Veeam ONE now fully supports Microsoft SQL Server 2017.
  • Microsoft Windows Server 2016 Version 1709 Support.  Veeam ONE now fully supports Microsoft Windows Server 2016, version 1709

Monitoring 
 
  • Veeam Agent Jobs Monitoring. Veeam ONE now monitors Veeam Agent backup jobs configured in Veeam Backup & Replication servers
  • Veeam Agent Policies Monitoring. Veeam ONE now monitors Veeam Agent backup policies configured in Veeam Backup & Replication servers
  • Enhanced Veeam Backup Data Collection. With Update 3, users will experience faster data collection from Veeam Backup & Replication servers, especially in large-scale deployments.
  • Enhanced Hyper-V Data Collection. With Update 3 users will experience more stable data collection from Microsoft Hyper-V, especially in large-scale deployments.
  • Veeam ONE Server Load Alarm. This alarm notifies user of high Veeam ONE server load to ensure stable workload.
  • Performance Cache Path Setting. Veeam ONE now allows to change the performance cache location in Monitor Client UI.

Reporting
 
  • Protected Computers Report. This report lists all protected and unprotected computers running Veeam Agent.
  • Data Sovereignty Overview. This report lists all protected objects, backups and replicas grouped by location tag
  • Data Sovereignty Violations. This report shows potential data sovereignty violations for all protected objects.
  • Location-Based Reporting.  Veeam ONE now provides an option to generate reports based on the location tags configured in Veeam Backup & Replication
  • New VM Metrics. Veeam ONE now includes “VM Used Space per Datastore” and “VM Provisioned Space per Datastore” counters to identify how much space a VM and its corresponding files take up on the datastore.
  • Enhanced Backup Custom Infrastructure Report. “Last Run Duration (sec)” has been added to the report parameters list.  

Veeam Cloud & Service Providers
 
  • Cloud Connect Inventory Report Enhancement.  This report now displays per-VM license key usage.
  • Enhanced vCloud Director integration. Veeam ONE now caches user credentials to allow faster log-ins to the Monitor client. 
  • Tenant Credentials Caching. This feature Veeam ONE saves permissions check time over infrastructure each time a tenant logs in.

Resolved Issues


Monitoring



General
  • Performance graphs do not handle daylight saving time

Backup
  • Under certain conditions tape server summary displays incorrect number of processed VMs.
 
vSphere
  • Guest OS disk usage alarm is reset to its default thresholds after product update.
 
Hyper-V
  • Some performance-based alarms ignore custom “Time period” values.
  • CSV datastores with the same name managed by the same SCVMM server display incorrect values.

Reporting
 
General
  • Report scheduling does not handle daylight saving time
  • Several reports miss data in Advanced Scalability mode
  • Direct links to Veeam ONE dashboards and reports integrated to 3rd party monitoring and reporting applications stop working after upgrade.
  • Deleted VMs are not considered in performance-based chargeback reports
 
Backup
  • Under certain conditions Cloud Connect User Report (Backup) shows incorrect number of Days Left to Reach Quota.
  • VM Change Rate History report shows not accurate number of incremental backups
  • Latest Backup Job Status report treats job retries as individual job runs
 
vSphere
  • Capacity Planning report shows incorrect datastore usage
 
Hyper-V
  • Some reports show wrong vCPU count for VMs using NUMA
  • Under certain conditions Host Resource Usage Chargeback report uses VM Disk size in TB instead of GB what makes VM cost calculation results incorrect
     
Business View
  • Tags are not collected from distributed vCenter Server 6.x when Platform Service Controller is installed as a dedicated server
  • Under certain conditions VMs with long VM Folder path cannot be categorized
 
Known Issues
 
  • Dashboard scheduling doesn’t work in distributed Veeam ONE installation when security certificates are missing from the server with Veeam ONE Web UI. To resolve this problem, import security certificates that are installed to Veeam ONE server to the server where Veeam ONE Web UI is deployed.
  • Performance collection of CSV under Hyper-V cluster stops after volume is renamed. To resolve this problem, restart Veeam ONE server service.
  • Data Sovereignty Violations report requires Microsoft SQL Server 2012 or newer.
 
 

More Information

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

MD5 checksum for VeeamONE_9.5.0.3801.Update3.zip: 6C4D70248B2983BC4E9523B7878A87EC

If you are looking for Veeam Backup & Replication 9.5 Update 3, please follow this link.

Release Notes for Veeam Backup & Replication 9.5 Update 3

$
0
0

Challenge

Release Notes for Veeam Backup & Replication 9.5 Update 3

Cause

Please confirm you are running version 9.5.0.580, 9.5.0.711, 9.5.0.802, 9.5.0.823, 9.5.0.1038 or 9.5.0.1335 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.1536.

Solution

As a result of on-going R&D effort and in response to customer feedback, Update 3 includes hundreds of enhancements and bug fixes, the most significant of which are listed below.

New features

Built-in agent management. Veeam Agent for Microsoft Windows and Veeam Agent for Linux can now be deployed and managed directly from the Veeam Backup & Replication console, adding support for physical and cloud workloads protection.
  • Maintain complete control of data protection for ALL your virtual, physical and cloud workloads by managing both hypervisor-based and agent-based backups natively through the Veeam Backup & Replication console.
  • Ensure no Windows or Linux computers are left unprotected by centrally deploying Veeam agents with automated host discovery via dynamic protection groups based on Active Directory containers, or CSV files exported from your existing CMDB system.
  • Protect Microsoft Windows Server Failover Clusters with new agent-based backup jobs with support for SQL Server failover clusters and SQL Server AlwaysOn Availability Groups – including support for guest file and application item recoveries from cluster backups.
Insider protection for Veeam Cloud Connect. Ensure the ability to recover your data following a cyber-attack by having your Veeam Cloud Connect service provider protect your data against insider attacks. Service providers can now enable protection of your backups against accidental or malicious deletion directly from the Veeam Backup & Replication console. These deletions are often executed either by hackers who have breached the tenant’s network perimeter and obtained powerful credentials with a brute force attack (with the intention of deploying ransomware on the production servers), or by disgruntled employees.

Data location tagging. Ensure data sovereignty compliance required by various regulations, such as the General Data Protection Regulation (GDPR), by tagging production infrastructure and backup infrastructure objects with locations. Location tags are used to prevent accidental errors when configuring backup and replication jobs or performing out-of-place restores, by issuing a warning when an action may result in a data sovereignty violation and producing audit trails whenever such action is confirmed. Additionally, new Veeam ONE reports use location data to help prove compliance.

IBM Spectrum Virtualize Integration. Reduce the impact on production environments and achieve lower recovery time and point objectives through new storage snapshots integration for IBM Storwize, IBM SAN Volume Controller (SVC) and any other IBM Spectrum Virtualize based storage system, such as Lenovo Storage V series or IBM/Cisco VersaStack.

Universal Storage Integration API. The new storage array integration framework included in Veeam Backup & Replication starting with this update enables select storage partners to build integrations of their primary storage systems with advanced Veeam Backup & Replication functionality that leverages storage snapshots.

Platform support
  • Microsoft Azure. Direct Restore to Microsoft Azure functionality has been update to support 4TB virtual disks, Azure Germany and Azure China.
  • Microsoft SQL Server 2017 support for application-aware processing on Windows-based virtual machines, including transaction log backup and point-in-time restores; and as a backend configuration database for the Veeam Backup & Replication itself.
  • Microsoft Windows 10 Fall Creators Update support as guest virtual machines, and for installation of Veeam Backup & Replication and all of its components.
  • Microsoft Windows Server 1709 support as guest virtual machines, and for installation of Veeam Backup & Replication remote components.
  • Microsoft Windows Server Hyper-V 1709 support as a hypervisor host, including support for virtual hardware version 8.2 virtual machines.
  • VMware Cloud on Amazon AWS support allows protecting VMs running in the cloud, and migrate or replicate workloads from on-prem vSphere deployment to VMC (and vice versa).
  • VMware vCloud Director 9.0 compatibility.
Storage support
  • Cisco HyperFlex support of deployments with multiple appliances under a single vCenter Server.
  • DELL EMC Data Domain integration now supports Data Domain systems running DD OS 6.1
  • HPE 3PAR StoreServ integration has been extended to include snapshot-only backup jobs; ability to retain primary storage snapshots created by backup jobs with a different retention policy; and ability to perform backup from storage snapshots from secondary 3PAR array running in Peer Persistence mode.
  • Hyperconverged infrastructures (HCI) deployments can now leverage the new option to force the load balancer to use Direct NFS backup proxy located on the same vSphere host with the processed virtual machine, to avoid stressing storage replication network with backup traffic . To enable this functionality, create EnableSameHostDirectNFSMode (DWORD) value under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication registry key on the backup server. The value is used to controls failover behavior when Direct NFS proxies if the proxy on same host is unavailable: 1 allows failover to other Direct NFS proxies, and 2 restricts failover to NBD only.
  • LTO-8 support for all tape-related functionality.
Backup Copy
  • Backup mapping for agent backup files is now supported to enable scenarios such as backup seeding.
  • Restore from backup copies. When initiating a restore from local user interface, Veeam Agent for Microsoft Windows and Veeam Agent for Linux will now provide the ability to pick a restore point stored in the secondary repository, should backup files in the primary repository be missing.
Hyper-V
  • Hyper-V 2016 VMs with non-snapshottable disk such as disks connected via in-guest iSCSI initiator can now be processed by backup and replication jobs, with unsupported disks skipped and their content not included in a backup or replica. If you’d rather prefer the job to fail on such VMs (legacy behavior), create HyperVIgnoreNonSnapshottableDisks (DWORD) value under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication registry key on the backup server.
Oracle
  • New Oracle 12.2 account types support includes Microsoft Windows Group Managed Service Accounts (gMSA) and Microsoft Windows Virtual Accounts.
VMware
  • VMDK resize operation will no longer result in resetting CBT data for all virtual machine disks, but rather for the resized disk only.
  • Non-encrypted NBD transport is again availble for vSphere 6.5, significantly improving backup and replication performance comparing to previously forced NBDSSL.
Veeam Cloud & Service Provider Partners
9.5 Update 3 includes many new features and enhancements for service providers offering Veeam Cloud Connect services. For the full list of these enhancements and bug fixes, please see this topic on the private VCSP forum. Not a member of the VCSP forum? Click here to join.

This update also resolves the following common support issues:
  • Backup Copy jobs should no longer copy weekly GFS fulls twice under certain circumstances, and should now correctly extend copy interval when processing active full backups.
  • File-level recovery in the Enterprise Manager should now work more reliably from non-Windows virtual machines, and after source Hyper-V VM was migrated to another host within SCVMM.
  • Linux-based backup repository registered under root account should no longer crash when Data Mover crashes for whatever reason.
  • Building VM list operation accelerated up to 4 times for Hyper-V jobs configured to use SCVMM tags.
  • Reliability enhancements with Hyper-V backups in off-host backups and guest processing logic.
  • Prefix for worker storage snapshots was changed from “Veeam_” to “VeeamAUX_” due to too many users using the original prefix in day to day operations, which made Veeam skip those snapshots.
  • Direct Restore to Microsoft Azure should now tolerate short term Azure connectivity disruptions, uses more firewall friendly port 443 by default, and supports Azure accounts with multiple directories (use AzureDefaultTenantIdGUID registry value to set GUID of the directory to use).
  • VeeamZIP retention should now work correctly with all System Locales.

More Information

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

MD5 checksum for VeeamBackup&Replication_9.5.0.1536.Update3.zip is 7f5da81733eb57375c62fbcc5c937ecc 

vCenter tags collection/assignment using PowerCLI tool

$
0
0

Challenge

In some cases, Veeam ONE cannot collect or assign vCenter tags properly in vCenter 5.x versions. You can identify the issue by the following error messages in Veeam ONE Reporter logs:
 
Failed to execute SOAP command "CInvSvcCreateCategory". Inventory Service was not created.
Can not Create tag with EXCEPTION: CreateCategory failed.
Failed to dispose inventory service proxy EXCEPTION: The remote server returned an error: (401) Unauthorized.

NOTE: In order to export the logs, follow this KB article.

Cause

Veeam ONE uses PowerCLI to collect and assign tags in VMware vCenter 5.x.

Solution

Proceed with these steps to implement an alternative tags collection/assignment method:

1. Check whether the account used to connect vCenter Server and ESX(i) hosts has all the necessary permissions assigned.
2. Install Veeam ONE 9.5 Update 3.
3. Install PowerCLI 6.5 on Veeam ONE server.
4. On the Veeam ONE server:
  • Open Windows registry editor snap-in and navigate to the following registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise\
  • Create a new registry key or modify the existing one:
Name:  TagsCollectingMethod
Type:   DWORD
Value:  1

5. Restart Veeam ONE services to apply the changes.

More Information

Should you have any questions, contact Veeam Support.

Creating a VMware ESXi extension (VIB) for Veeam Backup from Storage Snapshot with Cisco HyperFlex IOvisor processing

$
0
0

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 SLES11

SLES11 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
User-added image

b. Copy the VIB file to the ESXi host's tmp folder using HTTP or a SCP client
User-added image

c. Install the VIB
Command:
esxcli software vib install -v /tmp/VeeamCiscoHXFirewall.vib -f

User-added image

d. Verify that the VIB was installed
Command:

esxcli software vib list | grep 'Veeam'
User-added image

e. Verify that the new firewall rule is active
Command:
esxcli network firewall ruleset list
User-added image

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
User-added image

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"
User-added image

3. Verify that the IPs are set
Command:
esxcli network firewall ruleset allowedip list | grep -v "All"
User-added image


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
User-added image

2. Check the VIB
esxcli software vib list | grep 'Veeam'
User-added image

3. Check the ruleset
esxcli network firewall ruleset list
User-added image

4. Check which Veeam Proxy IPs are assigned
esxcli network firewall ruleset allowedip list | grep -v "All"
User-added image
 

vCenter tags collection/assignment using PowerCLI tool

$
0
0

Challenge

In some cases, Veeam ONE cannot collect or assign vCenter tags properly in vCenter 5.x versions. You can identify the issue by the following error messages in Veeam ONE Reporter logs:
 
Failed to execute SOAP command "CInvSvcCreateCategory". Inventory Service was not created.
Can not Create tag with EXCEPTION: CreateCategory failed.
Failed to dispose inventory service proxy EXCEPTION: The remote server returned an error: (401) Unauthorized.

NOTE: In order to export the logs, follow this KB article.

Cause

Veeam ONE uses PowerCLI to collect and assign tags in VMware vCenter 5.x.

Solution

Proceed with these steps to implement an alternative tags collection/assignment method:

1. Check whether the account used to connect vCenter Server and ESX(i) hosts has all the necessary permissions assigned.
2. Install Veeam ONE 9.5 Update 3.
3. Install PowerCLI 6.5 on Veeam ONE server.
4. On the Veeam ONE server:
  • Open Windows registry editor snap-in and navigate to the following registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise\
  • Create a new registry key or modify the existing one:
Name:  TagsCollectingMethod
Type:   DWORD
Value:  1

5. Restart Veeam ONE services to apply the changes.

More Information

Should you have any questions, contact Veeam Support.

VMware Cloud on AWS Support. Considerations and Limitations

$
0
0

Challenge

Some of VMware features and permissions are not granted by default at the start of VMware Cloud on AWS (VMC). Thus, some depending Veeam Backup & Replication features will be limited or not operating. Depending on VMware update releases for VMware Cloud on AWS, the situation may change and the features from the table below may become available. Please contact your VMware administrator for timely update.

Solution

Affected Veeam FeatureLimitationWorkaround

Instant VM Recovery

Currently, VMware Cloud on AWS (VMC) does not allow for NFS usage

Use IVMR from a backup copy on-premises.
Use a combination of a Veeam backup job and replication job for proactive restore capabilities

Other OS File Level Recovery

Currently, VMC does not allow for NFS

Start Linux File-Level Recovery from a backup copy on-premises

Quick Migration               

Quick Migration cannot migrate VMs to VMC if they are running

Use Veeam Replication and permanent failover to achieve similar functionality
For Free Edition, shutdown the VM before migration

SureBackup, Sure Replica, OnDemand Labs, Virtual Lab

Currently, VMC  does not allow NFS and network manipulation

As for SureReplica, you can perform it if the replication target is a non-VMC vSphere environment (e.g., replicate VM from VMC to on-premises)

VM Guest Interaction and Windows File Restore by VIX or WebService API

Currently, VMC does not allow usage of VMware Webservice API

If you want to perform Veeam Guest processing or Windows File-Level Recovery, then connect to a VM over the network from Veeam Backup & Replication

VM Replication ReIP

ReIP is not available on VMC

 

Windows Dynamic disks are not supported

Currently, VMC does not allow to process dynamic disks at Hot-Add (Virtual Appliance mode) backup

VMware will provide a hotfix for this soon

Non-Unicode VM names

Currently, VMC does not allow non-Unicode characters for VM names within their APIs used ad VMC

 

VM Replication based File Level Recovery

 

Use file restore from backups or use a VM replica on a non VMC environment to start the File recovery

    More Information

    Problem:

    Impossible to add the VMware Cloud on AWS vCenter server to the managed server, or VMs within this vCenter are not visible in the list of VMs.

    Solution:

    1. Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
    2. When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmc.vmware.com.

     

    Problem:

    When working with Restore or VM Replication wizard, users may face some issues accessing VMware Cloud on AWS vCenter server.

    Cause:

    By design, VMware does not provide customers access to the background infrastructure and used datastores.

    Solution:

    For proper operation, you can select the specific areas marked as “Workload” or “Compute”. Avoid using the non-accessible areas, for example:

    • vsanDatastore datastore
    • Management VMs folder
    • Mgmt-ResourcePool resource pool

    HCL - JetStor X Series

    $
    0
    0

    Challenge

    Product Information

    Product Family: JetStore X Series 
    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: 824iXD 
    Number of Drives: 8 
    Drive type: SAS SSD (RAID0) 
    Firmware version: 1.2.1 
    Connection protocol and speed: 10GB iSCSI 
    Additional support: All models and configurations of JetStor X series with equal or above the one outlined above 
    General product family overview: AC&NC / JetStor X series is the high performance, simple, secure, and scalable SAN storage systems for Enterprise and SMB. It is an ideal solution to the applications of mission critical data center, virtualization integration, media and entertainment, or large scale surveillance; and also Backup and disaster recovery in enterprise, SMB or ROBO (Remote Office/Branch Office) deployments. 
     
    Our JetStor storage platforms integrate the fastest connectivity, architectures, and processors with proven durability, plug’n play ease, and functionality like deduplication and tiering.  JetStor Storage arrays offer a selection of SAN (Fibre channel or iSCSI) or NAS connectivity with multiple host ports for parallel-path performance or clustered environments.  We provide all-flash arrays for maximum I/O applications, SAS and SATA systems for economical storage, and hybrid systems. Whether for file, block, or unified storage, JetStor solutions are engineered for scalability and uncompromising performance. 

     

     

    Veeam Details

    Veeam Build Number: 9.5 
    Veeam Settings:  

    • Repository Type: Windows 
    • Deduplication: Yes 
    • Compression: Optimal 
    • Storage Optimization: Local Target  
    • Per-VM Backup Files: No 
    • Decompress before storing: No 
    • Align backup file blocks: No 

    More Information

    Company Information

    Company name: AC&NC / JetStor 
    Company overview: AC&NC™ / JetStor meets the evolving needs for data storage, protection, and management. We leverage leading technologies to offer high-value solutions for NAS, SANs, clouds, and hyper-converged infrastructures (HCIs).  Since 1994, our customers have spanned virtually every industry, and range from Fortune 500 enterprises to small and medium-sized firms.  We support environments from data centers and clouds to branch offices and remote sites. 

    AC&NC provides individual components, custom builds solutions or delivers infrastructure as a service.  We can supply purpose-built storage appliances or entire racks and stacks, including storage, servers, switches, and software. www.acnc.com 

    Invalid NEA Name during NEA Deployment

    $
    0
    0

    Challenge

    Due to a recently discovered issue, please do not attempt to deploy a network extension appliance without a name.
     

    Solution

    The name must contain at least one alpha-numeric character.

    Veeam Availability Console 2.0 Hotfix_1332

    $
    0
    0

    Challenge

    Veeam Availability Console 2.0 Hotfix_1332

    Cause

    This update resolves the following issues that can be encountered with Veeam Availability Console (VAC) 2.0:

    1) 100% CPU load while adding a Company to the VAC console.

    2) Issues with Company Cloud Host Memory Quota and Company Cloud Host Storage Quota alarms.

    3) Veeam Agent for Microsoft Windows in the 'Warning' state disappears from the VAC views after applying the policy.

    4) All VAC agents become 'Out-of-date'.
     

    Solution

    Before you begin, confirm under Windows > Programs and features that the current product version is 2.0.1.1319.

    Download VAC 2.0.1.1332.

    To install the update, on the VAC server execute VAC.ApplicationServer.x64_2.0.1.1332.msp as administrator, or run this cmdlet as administrator: 
     
    msiexec /update c:\VAC.ApplicationServer.x64_2.0.1.1332.msp 

    More Information

    You can check whether the update installed successfully opening Windows > Programs and features
    The product version for Veeam Availability Console will be 2.0.1.1332 after applying the update.

    Should have any questions, contact Veeam Support.

    Keyexchange error on Linux managed server after updating the kernel

    $
    0
    0

    Challenge

    Steps to correct Keyexchange errors on newly updated Linux managed server

    Cause

    Veeam SSH client caches both the Key and the encryption method. If the Linux kernel depreciates an encryption method when the kernel updates, connections to the managed server may fail with error such as “Server does not support *key method* for keyexchange” 

    Solution

    Currently the only way to correct this is to navigate to “Backup Infrastructure,” open the properties of the managed server, and “next, next, finish” through the properties to refresh the SSH client cache.

    How to configure antivirus exclusions to prevent interaction with Veeam Backup & Replication

    $
    0
    0

    Challenge

    This article documents antivirus exclusions that have been found to help prevent antivirus software from interrupting Veeam Backup & Replication communications with components such as proxies and repositories or with the guest OS of VMs that are being backed up or replicated.

    Cause

    In some rare instances antivirus can prevent certain executables, processes, or agents from being correctly deployed or leveraged from the Veeam server, proxy, repository, or even the guest OS.

    Solution

    Antivirus Exclusions:

    Folders on the Veeam Server:
    C:\Program Files\Veeam
    C:\Program Files (x86)\Veeam
    C:\Program Files\Common Files\Veeam
    C:\Program Files (x86)\Common Files\Veeam
    VBRCatalog ( [HKLM\SOFTWARE\Veeam\Veeam Backup Catalog] CatalogPath value)
    NFS (Configured in each repository, stored in [HKLM\SOFTWARE\Wow6432Node\Veeam\Veeam NFS] RootFolder value)
    C:\VeeamFLR\*
    C:\Windows\Veeam

     
    Folder on Guest OS for VSS:
    C:\Windows\VeeamVssSupport
    C:\Windows\VeeamLogShipper

    Folders on VMware Backup Proxies and CIFS Repository Gateway:
    C:\Program Files(x86)\Veeam
    C:\Windows\Veeam


    Folders on Windows Repositories:
    C:\Program Files(x86)\Veeam
    C:\Windows\Veeam
    *Also include the path the backup files*
     
    Folders on WAN Accelerator:
    C:\Program Files(x86)\Veeam
    C:\Windows\Veeam
    *Path of WAN cache on WAN accelerators*


    Files:
    VeeamAgent.exe
    VeeamAgent64.exe
    *.vmdk
    *.flat
     
    Due to the complex nature of antivirus software some additional exclusions may be needed.
    If your antivirus has a logging or history system please review this to see actions it may have taken that may affect Veeam Backup & Replication operations.

     

    How to Use the Veeam Backup Validator

    $
    0
    0

    Challenge

    This article will document how to use the Veeam Backup Validator command line tool.
     
    Note: Some command line options shown below are only available in v8 and v9. Previous versions had reduced functionality. To see what options are available, execute the command line application with the parameter /?.

    Solution

    The Veeam Backup Validator can be found in the installation folder for Veeam Backup & Replication.
         Default Install Path: C:\Program Files\Veeam\Backup and Replication\Backup
         If the path was changed on install, you can find the path in the registry:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication] CorePath
     
    Syntax:
     
    Veeam.Backup.Validator.exe /backup:backupname|backupid [/vmname:vmname]
        [/point:pointid] [/date:pointdate] [/time:pointtime] [/silence]
        [/skip] [/report:reportpath [/format:xml|html]]
     
    Veeam.Backup.Validator.exe /file:backupfile{1..*} [/vmname:vmname] [/silence] [/skip]
        [/report:reportpath [/format:xml|html]]
     
    Parameters:
     
        /?       - Displays help
        /backup  - Specifies backup name or backup ID
        /vmname  - Specifies one or more VM names (empty value for all VMs)
        /point   - Specifies restore point ID
        /date    - Specifies restore point date
        /time    - Specifies restore point time
        /silence - Enables silence output mode
        /skip    - Skips specified VMs
        /report  - Generates HTML report at the specified path
        /file    - Specifies one or more backup files (VBM, VBK, VIB, VLB)
        /format  - Specified report format (HTML, XML) 

       /username:username - Specifies username for network share
       /password:password - Specifies password for network share

    Examples:   
    • Validate the VMs named "W2008", "W2008R2_DC" and "W2K" in the most recent restore point for the backup "Backup Job 1_imported".

      Veeam.Backup.Validator.exe /backup:"Backup Job 1_imported" /vmname:W2008 /vmname:W2008R2_DC /vmname:W2K

       
    • Validate all virtual machines in the last restore point with ID 3942788C-B309-4FA4-A111-A4C87B3EC63D.

      Veeam.Backup.Validator.exe /backup:3942788C-B309-4FA4-A111-A4C87B3EC63D

       
    • Validate a VM with the name "Windows 8" in the restore point created on December 5 2012 for a job named “Backup Job 1".
       
      Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"Windows 8" /date:05.12.2012

       
    • Validate a VM with the name "VM1" in the restore point created around 16:00 on December 5 2012 for a job named "Backup Job 2".

                Veeam.Backup.Validator.exe /backup:"Backup Job 2" /vmname:"VM1" /date:"05.12.2012" /time "16:00"
     
    • Validate a VM with the name "VM2" contained in the VBM file located at C:\Backup\VM2_Backup.vbm

      Veeam.Backup.Validator.exe /file:"C:\Backup\VM2_Backup.vbm" /vmname:"VM2"

       
    • Validate all VMs in VBK-file (backup file).

      Veeam.Backup.Validator.exe /file:"C:\Backup\VM2_Backup.vbk"

       
    • Validate a VM with the name "VM3" in the most recent restore point of "Backup Job 1" and create an HTML-report.

      Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"VM3" /report:"D:\Reports\Backup_Job_1_Validate_30_09_2014.html"

       
    • Validate a VM with the name "VM3" in the most recent restore point of "Backup Job 1" and create XML-report.

      Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"VM3" /report:"D:\Reports\Backup_Job_1_Validate_30_09_2014.xml" /format:xml
     
    • Validate a backup file.

      Veeam.Backup.Validator.exe
      /file:"\\192.168.1.5\TestShare\Empty VM encryptedD2017-09-22T172639.vbk"

    More Information

    Note:
    1. The date format that must be used is based on the regional settings of the computer the tool is run on. If the system is configured to have mm.dd.yyyy, as opposed to dd.mm.yyyy, please use that date format
    2. Backup Validator must be started with Administrator privileges
    3. When files are located on network share you need to specify the whole path (ex.: \\192.168.1.5\TestShare\Empty VM encryptedD2017-09-22T172639.vbk).
    4. Mapped network drives (net use z: \\192.168.1.5\TestShare) are not supported.

    Azure Government support

    $
    0
    0

    Challenge

    Starting from Veeam B&R 9.5 Update 3 it is possible to use Azure Government accounts

    Solution

    In order to enable Azure Government, follow these steps:
    1. Download and apply the registry file
    2. Restart Veeam Backup Service (note that it will interrupt all running jobs)
    3. Add an Azure account

    More Information

    In order to revert to using usual Azure accounts, remove the following registry values under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\:
    AzureEnvironmentVariables
    AzureASMImageName

    Restart Veeam Backup service to apply changes.
    Viewing all 4486 articles
    Browse latest View live


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