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

Backup configuration is not saved after configuring backup job

$
0
0

Challenge

After installing Veeam Agent for Microsoft Windows and configuring a backup job, the settings are not shown in the Control Panel, and Veeam Agent for Microsoft Windows keeps prompting to configure backup settings.

Cause

The Windows OS was installed with non-English region and culture settings. As a result, these settings were applied to the Windows system account.

Solution

You will need to set Format to English (US) for the system account.

Go to the Region settings (press Win + R > type intl.cpl > press Enter)
  1. On the Formats tab set Format to English (US)
  2. On the Administrative tab click Copy Settings and check that Format is set to English for Current user
  3. Enable the Welcome screen and system accounts checkbox on the same tab
  4. Press OK and restart your machine
Once the necessary changes are applied to the system account, a non-English Format can be set for the Current user account. Note, that the Format has to remain English (US) for the system account.

More Information

Here is an example of a working configuration:

User-added image

Your backup target does not support this product version and needs to be upgraded

$
0
0

Challenge

During an upgrade from Veeam Endpoint Backup Free to Veeam Agent for Microsoft Windows 2.0, you receive the following warning:

Your backup target does not support this product version and needs to be upgraded
User-added image

Cause

If Veeam Agent for Microsoft Windows is to be integrated with Veeam Backup & Replication, version 9.5 Update 2 of the latter is required.

During the upgrade, Veeam Agent for Microsoft Windows checks the latest backup made by Veeam Endpoint Backup Free and gets the information about Veeam Backup & Replication version.

However, Veeam Endpoint Backup Free is not aware of the updated Veeam Backup & Replication server unless a backup job has been run after the upgrade to 9.5 U2.

Solution

Either
disregard the warning message

or
run a backup with Veeam Endpoint Backup Free 1.5 to Veeam Backup & Replication before upgrading to Veeam Agent for Microsoft Windows 2.0.
 

Backup configuration is not saved after configuring backup job

$
0
0

Challenge

After installing Veeam Agent for Microsoft Windows and configuring a backup job, the settings are not shown in the Control Panel, and Veeam Agent for Microsoft Windows keeps prompting to configure backup settings.

Cause

The Windows OS was installed with non-English region and culture settings. As a result, these settings were applied to the Windows system account.

Solution

You will need to set Format to English (US) for the system account.

Go to the Region settings (press Win + R > type intl.cpl > press Enter)
  1. On the Formats tab set Format to English (US)
  2. On the Administrative tab click Copy Settings and check that Format is set to English for Current user
  3. Enable the Welcome screen and system accounts checkbox on the same tab
  4. Press OK and restart your machine
Once the necessary changes are applied to the system account, a non-English Format can be set for the Current user account. Note, that the Format has to remain English (US) for the system account.

More Information

Here is an example of a working configuration:

User-added image

How to Restore from Microsoft Exchange 2007 with Veeam Backup and Replication

$
0
0

Challenge

This KB article documents the procedure for restoring Exchange 2007 application items using a Surebackup job with export to PST.
 
Please note that as of April 2017, Microsoft no longer supports Exchange 2007. As such, steps 7 and 8 of this process are no longer supported by Veeam Technical Support.

Solution

Please Note: 
  • Veeam Backup & Replication must have an Enterprise or Enterprise Plus license to perform this restore.
1. Create a Virtual Lab.
  • On the proxy tab: Put the production NIC of the Virtual lab on the same network as the Veeam server, and either use DHCP if available in your environment or assign it an unused production IP.
  • On the networking tab: You will want to use "Advanced Single Host".
  • You'll want to configure the internal NIC in the "Network Settings" tab with the same IP address as the production default gateway on the network that the mailbox server and domain controller are connected to.
2. Create an application group.
http://helpcenter.veeam.com/backup/80/vsphere/appgroup_create.html

Add to it the following servers in the order listed here:
     • Domain Controller w/ Global Catalog role
     • Exchange Mailbox server
     • Exchange CAS server (if separate).
 
Note: In the application group settings, enable the "Domain Controller" role for the DC and remove all test scripts.
For the Exchange server, leave all roles unchecked. Disable the IP boot verification tests on all servers in the application group, and set the application initialization timeout for all servers other than the DC to 0 seconds.

3. Create a Surebackup job.  
Configure it to use the Virtual Lab and Application Group configured in the previous steps.
Note:

     • On the Application Group tab, enable the “Keep the application group running once the job completes” option.
     • Do not configure any Linked Jobs

4. Run the Surebackup job.
Note: If you need to restore to a specific restore point choose the “Restore to…” option.

5. Wait for the job to report that all VMs in the SureBackup job are “Started”

6. Ensure Exchange Services are running.
Once the SureBackup job has been run and the required machines are up and running, connect to the CAS server and the Exchange server. Ensure that the Exchange Information Store service (MSExchangeIS) is running.

7. Make sure Outlook is installed on the CAS server.
     
The export-mailbox cmdlet that will be run later requires it.

8. Launch the Exchange Management Console PowerShell window run the following command to export the desired mailbox as a .pst file
  • export-mailbox –id ‘John Doe’ -PSTFolderPath z:\John.Doe.pst
When the export is finished, you can copy the file via Windows Explorer from the Veeam server by connecting to the CAS server using its masquerade IP (The first octet(s) can be obtained in the “vNIC Connection Settings” on the “Network Settings” page of the Virtual lab settings. The last octet(s) will be the production machine’s last octet(s)).
 
Common issues:
 
Make sure that if you are running a 32-bit machine, you download and use the 32-bit Exchange management tools.
https://www.microsoft.com/en-us/download/details.aspx?id=11876
 
If the Exchange restore point is older and the DC is brought up from a newer restore point, the trust relationship might be broken. If this is the case, you’ll need to log into the Exchange server as a local account, remove it from the domain, reboot, re-add it to the domain, reboot again, and from there you may continue with the restore process.

More Information

Reference KB’s
 
https://www.veeam.com/kb2047
 
https://www.veeam.com/kb2059
 

Release Notes for Veeam Management Pack 8.0 Update 4

$
0
0

Challenge

Release Notes for Veeam Management Pack 8.0 Update 4.

Cause

Please confirm you are running Veeam Management Pack 8.0 prior to installing this update. You can check this in Operations Manager console under Administration | Management Packs, the build number should be 8.0.0.2218 or later.

To install the update, import the management packs through Operations Manager console > Administration > Management Packs > Import Management Packs.

To obtain Veeam MP 8.0 for System Center - Update 4, please download it here.

Solution

New features:

- Veeam Integration Pack for Operations Management Suite
- Veeam VMware custom vCenter Alarm Monitor now supports VMs as target
- Improved Veeam Hyper-V Host CPU Scheduling Analysis monitor
- Datastore Unknown Files Analysis monitor supports Num Samples parameter
- Additional drill-down link in Veeam MP Analysis Reports

Resolved issues:

- Web console displays a blank page instead of Morning Coffee Dashboard
- ‘VMwareCluster.totalvMotions’ performance metric values not collected
- Hyper-V Cluster Disk counters display incorrect values
- False alerts from ‘Veeam Hyper-V VM Checkpoint Age’ monitor
- Empty Guest OS and Guest DNS name properties
- High memory usage causes Health Service restarts
- ‘Veeam Backup: Repository Connection Status’ availability monitor works as expected

More Information

To obtain Veeam MP 8.0 for System Center - Update 4, please download it here.

How to Restore from Microsoft Exchange 2007 with Veeam Backup and Replication

$
0
0

Challenge

This KB article documents the procedure for restoring Exchange 2007 application items using a Surebackup job with export to PST.
 
Please note that as of April 2017, Microsoft no longer supports Exchange 2007. As such, steps 7 and 8 of this process are no longer supported by Veeam Technical Support.

Solution

Please Note: 
  • Veeam Backup & Replication must have an Enterprise or Enterprise Plus license to perform this restore.
1. Create a Virtual Lab.
  • On the proxy tab: Put the production NIC of the Virtual lab on the same network as the Veeam server, and either use DHCP if available in your environment or assign it an unused production IP.
  • On the networking tab: You will want to use "Advanced Single Host".
  • You'll want to configure the internal NIC in the "Network Settings" tab with the same IP address as the production default gateway on the network that the mailbox server and domain controller are connected to.
2. Create an application group.
http://helpcenter.veeam.com/backup/80/vsphere/appgroup_create.html

Add to it the following servers in the order listed here:
     • Domain Controller w/ Global Catalog role
     • Exchange Mailbox server
     • Exchange CAS server (if separate).
 
Note: In the application group settings, enable the "Domain Controller" role for the DC and remove all test scripts.
For the Exchange server, leave all roles unchecked. Disable the IP boot verification tests on all servers in the application group, and set the application initialization timeout for all servers other than the DC to 0 seconds.

3. Create a Surebackup job.  
Configure it to use the Virtual Lab and Application Group configured in the previous steps.
Note:

     • On the Application Group tab, enable the “Keep the application group running once the job completes” option.
     • Do not configure any Linked Jobs

4. Run the Surebackup job.
Note: If you need to restore to a specific restore point choose the “Restore to…” option.

5. Wait for the job to report that all VMs in the SureBackup job are “Started”

6. Ensure Exchange Services are running.
Once the SureBackup job has been run and the required machines are up and running, connect to the CAS server and the Exchange server. Ensure that the Exchange Information Store service (MSExchangeIS) is running.

7. Make sure Outlook is installed on the CAS server.
     
The export-mailbox cmdlet that will be run later requires it.

8. Launch the Exchange Management Console PowerShell window run the following command to export the desired mailbox as a .pst file
  • export-mailbox –id ‘John Doe’ -PSTFolderPath z:\John.Doe.pst
When the export is finished, you can copy the file via Windows Explorer from the Veeam server by connecting to the CAS server using its masquerade IP (The first octet(s) can be obtained in the “vNIC Connection Settings” on the “Network Settings” page of the Virtual lab settings. The last octet(s) will be the production machine’s last octet(s)).
 
Common issues:
 
Make sure that if you are running a 32-bit machine, you download and use the 32-bit Exchange management tools.
https://www.microsoft.com/en-us/download/details.aspx?id=11876
 
If the Exchange restore point is older and the DC is brought up from a newer restore point, the trust relationship might be broken. If this is the case, you’ll need to log into the Exchange server as a local account, remove it from the domain, reboot, re-add it to the domain, reboot again, and from there you may continue with the restore process.

More Information

Reference KB’s
 
https://www.veeam.com/kb2047
 
https://www.veeam.com/kb2059
 

Enable SQL/Oracle Database exclusions from application-aware image processing

$
0
0

Challenge

A SQL or Oracle 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 and higher.
 

1. Close the Veeam Backup & Replication console.
2. Open Regedit.exe
3. Navigate to the key HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
4. Add a new DWORD ‘EnableDBExclusions’
5. Set the Value to 1

User-added image
6. Close the Registry Editor and open Veeam Backup & Replication
7. Open “Database Exclusions” from the Main Menu
User-added image

8. In the window that pops up, click Add.

9. Specify the DNS name (case sensitive) or the IP address and the instance name(case sensitive) that you wish to exclude from VSS Freezing and being Quiesced.

10. Specify the Database name (case sensitive) that you wish to exclude from application-aware image processing.

User-added image

On next job run the specified database will be excluded from the Application-Aware Image Processing freeze task.

Failed to allocate SCSI target ID... during HotAdd

$
0
0

Challenge

Whenever you use the Virtual Appliance (HotAdd) Transport Mode (Failover to network mode if primary transport modes fail or are unavailable is disabled) to back up the virtual machines, you may encounter an error stating that Veeam has failed to attach disks.
 

Cause

This is most likely caused by the lack of available SCSI ports on the proxy (VDDK logging shows "Failed to allocate SCSI target ID"). You can find the following entries in the agent logs (Agent.%VMname%.Hotadd.Attacher.log):
 
 < 388> vdl| 2017-01-08T07:03:14.974+01:00 error -[00388] [Originator@6876 sub=transport] Mounting VM vm-170 using transport hotadd failed : Failed to allocate SCSI target ID..\n
 < 388> vdl| 2017-01-08T07:03:14.974+01:00 error -[00388] [Originator@6876 sub=transport] Cannot use mode hotadd to access [TEST1234-LUN20-Mixed] VM02/VM02_1.vmdk: Cannot mount using this method. (Mounting VM vm-170 using transport hotadd failed : Failed to allocate SCSI target ID..)\n
[08.01.2017 07:03:14] < 388> vdl| VixDiskLib: Unable to locate appropriate transport mode to open disk. Error 13 (You do not have access rights to this file) (Mounting VM vm-170 using transport hotadd failed : Failed to allocate SCSI target ID..) at 4570.\n

 

Solution

Try adding more SCSI controllers to their proxy, or creating more proxies, or enable “Failover to network mode if primary transport modes fail or are unavailable” if it is disabled.
 

More Information

Adding a SCSI controller to the virtual machine (1037094)
 

Object "VM name" not found

$
0
0

Challenge

Job fails with the following error message, “Task failed Error: Object <vmname> not found”

User-added image

Check the log file for the following entries:
 
Error    Failed to expand object added to the job. Object: 'Object, id: , name: <vmname>, type: VM, vi type: VirtualMachine, host name: ’.
Error    Object <vmname> not found. (System.Exception)

The most direct resolution can be verified by editing the job, selecting the “Virtual Machines” tab, then selecting recalculate.

If any VM whose size comes back as “Not Available”, one should attempt the below as a resolution
.

Cause

This error is caused by the VM’s unique inventory reference identification number (MOREF, or Managed Object Reference) changing within the virtual infrastructure, or the VM having been deleted. Veeam is still attempting to find the VM by its old reference ID number based on a “find vm by NAME where REFID = X” query.

Note: The most common events that cause a VM MOREF ID to change are:
  • Reinstallation or creation of a new vCenter server where the old VC database is not reused.
  • A VM is removed from inventory and then added back to inventory.
  • In rare cases a host crash, which prompts the host to be removed and added back to the VC may cause the VMs on that host get new MOREF IDs.

Solution

Go to the Backup Infrastructure and rescan the vCenter Server.

Remove and re-add VMs affected by this behavior back to the job.

Please note that in version of Veeam Backup & Replication 6.1 and newer, the console session caches the Ref-IDs to make navigation faster. If the Ref-IDs have recently changed, the cache will most likely not have the correct Ref-IDs. To force the Ref-ID cache to be flushed, press the “Add” button and then click the refresh button within the “Add Objects” dialog.

User-added image

After you have flushed the cache, proceed to re-add the VMs to the job.

After you have added the VMs back to the job, click Finish. Then, open the job once more and repeat the “Recalculate” action.

All VMs should now correctly report their sizes and processes with this will now proceed in your Backup or Replication job.
Please be aware of that if the MOREFs were changed, Veeam sees the VMs as completely new ones, so on the next run Veeam will perform an active full for them.

Manually moving backup files to or from a Scale-Out Backup Repository

$
0
0

Challenge

You have backup files on a standard repository that you wish to move to a Scale-Out Backup Repository (SOBR).

Cause

Scale-Out Backup Repositories have special considerations for how backup files and metadata are distributed. Thus, simply copying files to one extent may be insufficient for a rescan of the repository to detect them properly and import them.
 

Solution

IMPORTANT: This process does not apply to Cloud Connect, and should not be used by providers. If you are a provider attempting to migrate tenant data to SOBR, please contact support for assistance.

If you have not yet created a SOBR:
  1. Create simple repositories, and at least one of them should be a path where backup files to be imported are stored (e.g., if backup files are in D:\Backups\Backup_Job_1\ then create a repository referencing the path D:\Backups).
  2. Re-scan the simple repository or repositories, and ensure all backups are imported.
  3. Create the SOBR and add the relevant repositories as extents.
  4. Within the creation process Veeam will inform via confirmation prompt that “Jobs and backups using this extent will be automatically updated to point to the scale-out backup repository.”
  5. User-added image
  6. If any jobs are not mapped to the backup files now within the SOBR, map them per the standard process.
     
If you have a SOBR and need to introduce new backups:
  1. Place the backup files to be imported in a temporary path. (e.g., if backup files are in D:\Backups, either copy or move them to D:\Backups-temp. A move is usually much faster.)
  2. Create a new simple backup repository that references this path (in our example, D:\Backups-temp).
  3. Re-scan the repository, and ensure all backups are imported.
  4. You can map the pre-existing job to the backup files’ new location now, or at the end.
  5. Edit your existing SOBR and add the new temporary repository to its list of extents.
  6. Place the new temporary repository extent in “Maintenance” mode.
  7. Evacuate the extent. Veeam will redistribute the backup files to other extents in the SOBR.
  8. If you did not map the original job in step 4, do so now.

If redistribution of files is not desired or necessary, you can simply copy the folder containing VBM and backup files to an existing extent. Rename both path and VBM to ensure import, and re-scan.

More Information

Note that if the VBM or the path to it does not conform to naming standards, Veeam Backup & Replication will fail to import it.
  • Allowed alphanumeric characters: a-z, A-Z, 0-9
  • Allowed special characters: _ - . + = @ ^
  • Must not contain spaces; use underscores in their place
 Moving backup files from one or multiple SOBR extents is viable as well. There are a few points to note:
  • Make sure to copy files from the backup chain from all extents.
  • SOBR backup chains are typically per-VM backup files. Simple repositories are typically per-job backup files. The chain will retain this method until an active full is run on the job to enforce the change.
  • The VBM file will exist in all extents. All VBMs for a particular backup job within a single SOBR should be identical. As a result, the target simple backup repository needs only contain one VBM.

There is no FIB [summary.xml] in the specified restore point

$
0
0

Challenge

Note: This KB is applicable to only 5.x and 6.x, if this issue occurs in a newer version a new Active Full must be ran.

Job fails with error "There is no FIB [summary.xml] in the specified restore point."

Cause

This error is referring to an FIB ( File in Backup ) that is missing from that specific point. The file that is missing is the summary.xml file, which is xml data that holds data about that point and what the point contains.

Solution

There are two options. Either, apply patch 1 and higher for version 6.1 of Veeam Backup & Replication, or upgrade to version 6.5, to prevent this from happening.
 
Running a full backup should allow the job to run again.

More Information

Here is a link to patch 1 for version 6.1: http://www.veeam.com/kb1671

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

$
0
0

Challenge

After installing Windows April update KB4015553 Veeam jobs and services fail at different operations with:
 
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"

Cause

This particular update (and all consequent rollups that include it) causes the system to run out of free RPC ports when there are failed iSCSI connections.

Solution

Repairing or removing unsuccessful iSCSI connections , followed by the server reboot, was found to fix the issue. If removing unused iSCSI connections remove any targets from the ‘Favorite Targets’ tab that are associated with these connections” as they may be reconnected after reboot.”

More Information

https://social.technet.microsoft.com/Forums/SharePoint/en-US/492f62ce-aec8-4777-98f0-0c9dbf302954/problem-with-kb4015553?forum=winserverwsus

Veeam ONE New DB creation

$
0
0

Challenge

Manual creation of the DB may sometimes be needed in specific environments

Solution

  1. Create Veeam ONE service account and assign in the following SQL permissions –
The account used to connect to the Microsoft SQL Server hosting the Veeam ONE database must have the following permissions:
  • Public role (default permissions)
  • CREATE ANY DATABASE permissions
  • db_owner role on the Veeam ONE database
  • db_datareader permissions on the master database
  • publicdb_datareaderSQLAgentUserRole permissions on the msdb database
  • [For Always-On Availability Groups] VIEW SERVER STATE permissions
The Named Pipes protocol on the Microsoft SQL Server must be enabled.
Note : If the Veeam ONE database runs on a remote Microsoft SQL Server instance, with the Microsoft SQL Server and Veeam ONE components residing in the same workgroup, Microsoft SQL Server authentication will be required.
  1. Create a new DB using the Veeam ONE service account that has the permissions specified above assigned.
  2. Run Script from Veeam ONE ISO – Addons\SQLScript\SQLScript.sql
  3. Install VeeamONE using the specified Service Account and DB. If Veeam ONE is already installed Specify DB using Veeam ONE settings utility located in C:\Program Files\Veeam ONE\Veeam One  Settings\VeeamOneSettings.exe
Start Veeam ONE
 

More Information

Please note that build number must match installed version, Additionally Manual Import of Reporter packs will be needed for reporter to operate.

Enterprise Plus license is required error on dashboards and reports

$
0
0

Cause

Veeam MP license is synchronized to the Data Warehouse then reports load this information. If license is invalid in the Data Warehouse due to Synchronization server having issue this error will occur.

Solution

  1. Open SCOM Operations Manager Console.
  2. Select Discovered Inventory
  3. Filter to Data Warehouse Synchronization server
If the server in question that shows in filtered list shows error or warning Microsoft support will need to be contacted to correct issue with Data Warehouse, then license will need reimported.

Failed to start service VeeamRSS issue

$
0
0

Cause

Sometimes we can run into a timeout issue when resource usage on a VM is high or it is under-provisioned.

Solution

Adjusting the timeout period for the VeeamRSS service.
 
1. In Registry Editor, right-click on the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
2. Next, right-click on Control (in the right-hand pane of the Registry Editor) and select New | DWORD. The name of the new registry entry will be selected for editing. Type "ServicesPipeTimeout" and then press ENTER.
3. Next, right-click on the new ServicesPipeTimeout registry entry and then click Modify.
4. In Edit DWORD Value, locate Value and then enter 180000.
5. Once finished, click OK. Then, restart the computer in order for the Service Control Manager to apply the change.
 
NOTE: TimeoutPeriod is a placeholder for the value of the timeout period in milliseconds that will be set for the service. For example, to set the timeout period to 24 hours (86400000 milliseconds), type 86400000.

Data Warehouse Permission issues

$
0
0

Cause

MP Version 8 uses dataset rules to collect host security profiles and snapshots. When a collector is installed on an agent, there is no issue. The data is forwarded to Management Server and written to DW under the DW account. When a collector runs on a Management Server which is our use case, the DW write is attempted under the HealthService run as account and fails.

Solution

1. Start SCOM Console and navigate to Administration > Run As configuration > Accounts and open Properties for your Data Warehouse Action Account > Distribution. Manually add your Management Server where the Veeam collector(s) is installed.
 
2. Open Profiles and double-click on Data Warehouse Account to open Run As Profile Wizard. Navigate to Run As Accounts. Click Add and select your "Data Warehouse Action Account". Then choose "Select class, group, or object" radio button and click Select > Object. Look for Veeam VMware Collector object there, select and add it. port Report Packs

More Information

The steps above are required to make sure that Run As accounts are correctly distributed to SCOM server that has a Veeam Collector role.

No data or old data in reports

$
0
0

Cause

Reports showing no data or old data when generated

Solution

Run collection manually:
  1. Open Veeam ONE reporter.
  2. Select Configuration Tab
  3. Select Object Properties Collection Task
  4. Click Run
  5. Once complete check report
  6. To prevent in future click Scheduling and adjust to a time closer to beginning of business day with an allotment of 1 to 2 hours for collection to complete

Veeam ONE Import Report Packs

$
0
0

Cause

Creation of New Database Manually, Corrupt Report packs

Solution

To import Report Packs
  1. Open Veeam ONE Reporter.
  2. Open the Configuration section.
  3. In the Configuration section menu, click Extension Modules.
  4. Open the Report management tab.
  5. Click Import.
  6. In the Import reports window, Navigate to the Veeam ONE ISO \Addons\Extension Modules. Then Import each report pack.

More Information

Veeam ONE Support can be contacted to assist with Import if needed.

Appliance Mode (Hotadd) Requirements and Troubleshooting

$
0
0

Challenge

Appliance mode (HotAdd) fails or configuration assistance is needed. 
The following is shown in the statistics window while processing a VM or could be found within the logs:
"HotAdd is not supported for this disk, failing over to network mode"

Solution

Requirements:

  1. If the Veeam Proxy being used to process the source VM is on a VMFS 3 datastore it must be formatted with proper block size to be able to mount the largest virtual disk of the hot added VMs:
    • 1MB block size – 256GB maximum file size
    • 2MB block size – 512GB maximum file size
    • 4MB block size – 1024GB maximum file size
    • 8MB block size – 2048GB maximum file size
  2. The Proxy being used to back up the VM must be a Virtual Machine on a host that is able to access the datastore where the source VM’s disks are stored
  3. For vSphere 5.1 the maximum supported VMDK size is 1.98 TB
  4. For vSphere 5.5 and older the maximum supported VMDK size is 62 TB
  5. The disks that are to be hotadd must be SCSI. IDE and pvscsi drives are not compatible with hotadd
  6. VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
  7. Datastore needs sufficient space for a VM snapshot

Known Issues:

  • If the VM disk resides on a Vvol the Hot Add Proxy VM's configuration files must also be on the same Vvol.
  • Hotadd may fail if any disk was created with a newer hardware version than the VM being backed up. For example, if a disk was moved from a hardware version 8 VM to a hardware version 7 VM. To resolve, upgrade the hardware version of the VM.
  • A single SCSI controller can have a maximum of 15 disks attached. To run multiple concurrent jobs with more than 15 disks, you need to add more SCSI controllers to your Veeam Proxy server that is responsible for hot adding the disks. (kb.vmware.com/kb/1037094)
  • In case of standalone host connection (no vCenter added to the console), you can only hot add disks of VMs which are located on the same host as the proxy server.  This may require additional proxy servers to be configured on each host in the environment.
  • Hotadd may fail if you are trying to back up the VM through the host added as a standalone server into Veeam Backup Infrastructure but actually being managed by vCenter. The following error message can be found in the source agent log:
    "Reconfigure attempt failed for VM "" with Vmomi::MethodFault::Exception ("vim.fault.HostAccessRestrictedToManagementServer")"
  • Hot Add may fail if the VM you are trying to back up and the proxy server are in different clusters.
  • Virtual Appliance backup job fails after you’ve cloned or restored your VBR server. The reason for that is incorrect UUID reference for Veeam Backup VM which can be found in the following registry key of the Veeam server. Please see http://www.veeam.com/kb1332
  • Hot Add fails if VM disks being backed up don't have unique ddb UUIDs across the Vcenter, for example if such VMs were deployed from a single template to different hosts.  Please refer to this Vmware article for details: http://kb.vmware.com/kb/2006865

Troubleshooting:

More Information

Please contact Veeam Technical Support for further assistance.

Release Notes for Veeam Backup & Replication 9.5 Update 1

$
0
0

Challenge

Release Notes for Veeam Backup & Replication 9.5 Update 1

Cause

Please note that this is an incremental update of the Veeam Backup & Replication version 9.5. If you are upgrading from previous versions of the product, please download the 9.5 full ISO image that already includes Update 1 from the general download page.
Please confirm you are running version 9.5.0.580, 9.5.0.711 or 9.5.0.802 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.823.

Prior to installing this update, please reboot the Veeam server to clear any locks on the product files. After reboot, please stop and disable all Veeam jobs, stop all Veeam services and apply the update. Once Veeam Backup Service starts, open the console and follow the Upgrade wizard to update all remote components.

Solution

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

Platform support
  • Dell EMC Data Domain OS 6.0 support, including synthetic full backup performances optimizations, backup retention and health check reliability improvements.
  • HPE 3PAR 3.2.2 MU3 support, including multiple storage API interaction improvements for added reliability and performance.
  • HPE StoreOnce 3.15.1 support, bringing Instant VM Recovery to Catalyst-based backup repositories.
  • Veeam Agent for Linux 1.0 support.
  • Veeam Agent for Microsoft Windows 2.0 Public Beta (build 2.0.0.594) support.
  • VMware vSAN 6.5 support.
  • VMware vSphere 6.5 support (see the next section for details).

VMware vSphere 6.5 support
  • Encrypted VMs support. vSphere 6.5 introduces VMs with encrypted disks. Such VMs can be backed up in hot add and network (NBD) transport modes only, with hot add mode requiring that the backup proxy itself is an encrypted VM. There are no limitations around restores, because backups contain unencrypted VM data (remember to enable backup encryption if that is a concern).
  • VMFS6 and VVOLs 2.0 support. vSphere 6.5 introduces the new versions of VMFS and VVOL (Virtual Volumes), which are fully supported with this update. This includes support for advanced functionality such as Backup from Storage Snapshots and Veeam Explorer for Storage Snapshots for VMs with virtual disks residing on VMFS 6 datastores.
  • Virtual hardware version 13 support. vSphere 6.5 introduces the new VM hardware version which increases some configuration maximums and adds ability to add NVMe controllers to a VM. This update adds ability to process such VMs.
  • NBD compression. VDDK 6.5 adds ability to enable native NBD traffic compression. To control the compression level, create VMwareNBDCompressionLevel (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server with value from 0 (no compression) to 3 (best compression). Please expect significant performance impact from enabling NBD compression unless you’re backing up over slow or busy management network.
  • New guest interaction API support. vSphere 6.5 discontinued VIX API that previous Veeam versions leveraged for network-less guest interaction for functionality such as application-aware processing. As part of vSphere 6.5 support effort, we have switched the corresponding functionality to the new vSphere API for guest interaction, so that you can continue using the existing product functionality with vSphere 6.5.
  • New VM tag API support. vSphere 6.5 introduces new APIs for programmatic access and management of vSphere tags. With its support by Veeam, you can continue using advanced backup policies based on tags even after you upgrade to vSphere 6.5

Engine
  • Double-byte support. Double-byte characters are now supported in the virtual infrastructure object names (such as VM name) and Veeam object names (such as job name).
  • Export performance improvements. Disk content export from agent-based backups now processes multiple disks in parallel, as opposed to sequentially.

Backup Copy
  • Performance improvements. Performance of Backup Copy jobs with large number of VMs (hundreds/thousands) was improved.
  • Reliability improvements. Added transfer resume functionality for transparent handling of short network connection outages in certain backup copy process phases where they were not previously used.

Tape
  • Reliability improvements. Added transfer resume functionality for transparent handling of short network connection outages between a source backup repository and a tape server.

File-level recovery
  • OES 2015 SP1 support. Open Enterprise Server 2015 SP1 support for file-level recovery from NSS volumes with Trustee Index enabled.

Self-service portal for vCloud Director
  • Side by side restore. Tenants are now able to restore VMs and vApps without overwriting the original object by selecting Keep restore option, in which case the restored object will be created with the _restored suffix as opposed to overwriting the original object (which is still possible by selecting Overwrite restore option).
  • Job mapping. Added Set-VBRvCloudOrganizationJobMapping PowerShell cmdlet that allows to map a vCloud backup job and associated guest processing credentials to the existing self-service org record to enable tenants to start using self-service portal functionality for the existing jobs and backups.

VMware
  • Direct SAN transport improvements. Improved direct SAN transport selection on backup proxies with disabled MPIO, added support for parallel restore through multiple Direct SAN backup proxies.
  • Restore without storage profile. The newly added Default policy container in the Select Datastore dialog allows restoring, replicating or migrating virtual machines without their virtual disks inheriting an existing storage profile assigned to the target datastore.
  • Restore logic improvements. Full VM restore and Instant VM Recovery operations will now preserve workingDir parameter of the original VM.
  • Broker service enhancements. Added experimental Broker Service behavior when it does not try to keep the vSphere infrastructure cache up-to-date continuously. Instead, it will query vSphere infrastructure hierarchy changes only when hierarchy data is requested, but no less often than the specified timeout. Using this mode significantly reduces vCenter Server traffic in large environments while only slightly delaying tasks requiring vSphere hierarchy data. To enable this mode, create VmwareForcedHierarchyUpdatePeriod (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server with the value in seconds (900 is the recommended value).

User interface
  • Asian OS locales support. Veeam Backup & Replication console now supports installation on operating systems with Asian locales, where it was previously unusable due to misplaced UI controls. Update 1 has been tested on all most common Asian locales and validated by local Veeam sales teams of the corresponding regions.
  • Experimental high DPI monitors support. We've made the first step towards high resolution monitors support - and while there's still work to be done, the UI is now more usable on DPI settings above 100%. This did require changing the UI font, resizing all dialogs and adjusting placement for some UI controls - so you will notice slightly different UI look after installing the update.
  • Wizard improvements. We've renamed the Next button before each step that applies the current settings into the configuration database to Apply in all wizards to make the consequences of clicking Next more obvious.
  • Support ID copy. By popular demand, we've enabled you to copy your Support ID from the License Information dialog into the Windows Clipboard.

This update also resolves the following common support issues:
  • Fixed an issue which caused monthly Active Full backup schedule to reset to the default one (First Monday of the month) after upgrading to version 9.5.
  • Improved reliability of establishing connections to Linux servers by addressing a number of Linux version-specific issues and updating SSH client.
  • Improved Direct Restore to Microsoft Azure proxy appliance deployment and management functionality.
  • Improved backup placement logic improvements for reversed-incremental backup jobs targeting scale-out backup repository with per-VM backup file chains disabled.
  • Addressed an issue with enabling CBT on a VMware VM when backup server is running on certain non-English locales, for example Turkish.
  • Addressed a number of minor issues with Veeam Cloud Connect.

More Information

Note: Veeam Backup & Replication 9.5 Update 2 is available. Click here to obtain it.

If you are looking for Veeam ONE 9.5 Update 1, please follow this link.
Viewing all 4478 articles
Browse latest View live


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