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

“VDDK Error: 1”


VM Count incorrect when using the “Update License key Automatically” feature

$
0
0

Challenge

When using the “Update License Key Automatically” or “Update now” feature in Backup and Replication the Protected VM count does not change.

Solution

This is by design currently.  When the Update License Key Automatically or Update Now feature is run, it only updates the expiration date of the license.  It does not update any additional information on the license.  Please update the license manually to get the license to reflect the proper information.  (Link to UG for installing license manually - https://helpcenter.veeam.com/docs/backup/vsphere/install_license.html?ver=95)
 
In addition, the Automatic License Usage Reporting (https://helpcenter.veeam.com/docs/backup/cloud/sp_license_usage_report_online.html?ver=95) does not work as intended as the updated Protected VM count does not update with the license.  Please use the manual license usage reporting (https://helpcenter.veeam.com/docs/backup/cloud/sp_license_usage_report_offline.html?ver=95).

 

More Information

We are looking to improve this feature in a future release, but for now this is working as designed. 
See https://www.veeam.com/kb2144 for information on Service Provider Licensing

 

Release Notes for Veeam Management Pack 8.0 Update 3

$
0
0

Challenge

Release Notes for Veeam Management Pack 8.0 Update 3

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.

After upgrade, the version of Management Packs will be 8.0.0.2372.

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

Solution

New features:

-    Support for all Microsoft 2016 Platforms (Windows Server, Hyper-V, System Center, SQL)
-    Support for vSphere 6.5
-    Support for Veeam Backup and Replication 9.5
-    Virtual SAN health check alarms monitoring
-    Authoring: custom vCenter Alarm monitor
-    Authoring: ESXi service status monitor
-    Show ESXi services task
-    Morning Coffee widget for custom dashboards
-    Hyper-V VM properties: Checkpoint Type, Shielded VM
-    Veeam Backup and Replication Scale-Out Backup Repositories Support
-    Veeam Broker Service Monitor
-    “Is Cloud Replica?” property for a Backup Job
-    Per-VM Backup license monitoring
-    Updated Hybrid Cloud Capacity Planning with new Azure sizes


Resolved issues:

-    Dramatically improved Hyper-V performance collection for CSV objects
-    Improved Veeam Backup and Replication Job RPO monitor
-    More granular Delegated Restore Permissions report
-    Snapshot Summary Report to include correct information about snapshots size
-    Instructions on configuring Dataset collection rules
-    Limit abnormal latency values received from vCenter 
-    Host Storage Sensor monitor is enabled 
-    Job Enabled and Schedule Enabled Backup Job properties added instead of single Enabled
 

More Information

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

List of Ports Used by Veeam Backup & Replication

$
0
0

Challenge

You would like to know the ports used for Veeam Backup & Replication and what they apply to.

Solution

VMware
Veeam Backup & Replication 9.5 - https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=95
Veeam Backup & Replication 9.0 - http://helpcenter.veeam.com/backup/vsphere/used_ports.html
Veeam Backup & Replication 8.0 - http://helpcenter.veeam.com/backup/80/vsphere/used_ports.html
Veeam Backup & Replication 7.0 - http://helpcenter.veeam.com/backup/70/vsphere/used_ports.html
Veeam Backup & Replication 6.5 - http://helpcenter.veeam.com/backup/65/vsphere/used_ports.html
 
Hyper-V
Veeam Backup & Replication 9.5 - https://helpcenter.veeam.com/docs/backup/hyperv/used_ports.html?ver=95
Veeam Backup & Replication 9.0 - http://helpcenter.veeam.com/backup/hyperv/used_ports.html
Veeam Backup & Replication 8.0 - http://helpcenter.veeam.com/backup/80/hyperv/used_ports.html
Veeam Backup & Replication 7.0 - http://helpcenter.veeam.com/backup/70/hyperv/used_ports.html
Veeam Backup & Replication 6.5 - http://helpcenter.veeam.com/backup/65/hyperv/used_ports.html

Veeam Backup & Replication console slow or unresponsive

$
0
0

Challenge

The Veeam Backup & Replication console is slow to respond when switching between different views. The issue is more noticeable when attempting to search through the history of jobs.

Cause

In rare cases the VeeamBackup SQL DB can have many thousands of previous task sessions which causes queries run by the console to be delayed.

Solution

There are two parts to resolving this, one resolves the issue in the short term by removing old sessions from the SQL DB, the other is to limit how many sessions are stored in the SQL DB.
 
──────────────────────────────────────────────────────────
Clearing old sessions from the SQL DB
──────────────────────────────────────────────────────────
Note: SQL Management Studio is required to perform this task. All jobs must be stopped. 
Note: This stored procedure removes sessions from the database, if the database contains many session entries this may take a very time (hours). Please plan accordingly.
  1. Stop all Veeam services.
  2. Connect to the SQL instance hosting the VeeamBackup database.
  3. Create a backup of the VeeamBackup database. (http://www.veeam.com/kb1471)
  4. Expand the DB to Programmability > Stored Procedures > dbo.DropStoppedOldJobSessions
  5. Right click > Execute... > in the window that appears enter how many days you want to keep
  6. Press OK to executeit will report “Query executed successfully.” when it completes.
  7. Start all Veeam services.
User-added image

──────────────────────────────────────────────────────────
Changing Session history retention
──────────────────────────────────────────────────────────
You can specify session history settings for jobs performed on the Veeam backup server. 
  1. Select Options from the main menu.
  2. Click the History tab.
  3. In the Sessions section, specify the number of sessions to display in the Sessions list of the History view.
In the Session history retention section, specify the number of sessions to keep in the Veeam Backup & Replication database.

User-added image

 

Moving Veeam ONE database to a different SQL Server

$
0
0

Challenge

You need to move the Veeam ONE database from the original SQL Server to a different SQL Server and change Veeam ONE Server configuration settings.

Solution

To change SQL Server or database connection settings for Veeam ONE Server, you can use the Veeam ONE Settings utility.

To modify connection settings, follow the instructions below.

Provision a domain account for Veeam ONE Monitor and Veeam ONE Reporter on the new SQL Server. This can be one account or two different accounts. Move the database to the new SQL Server. Depending on Veeam One version, grant the account(s) appropriate permissions:

 
Veeam One 6.xdb_owner 
Veeam One 7.xSystem Administrator
Veeam One 8.xSystem Administrator
Veeam One 9.0System Administrator
Veeam One 9.5Public role (default permissions)
CREATE ANY DATABASE permissions
db_owner role on the Veeam ONE database
public, db_datareader, SQLAgentUserRole permissions on the msdb database
 
NOTES:
  • The Named Pipes protocol on SQL Server must be enabled.
  • 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.

Next, modify the accounts that are used by monitoring and reporting components of Veeam ONE.

First, modify connection settings for Veeam ONE Monitor. To accomplish this, perform the following steps:
  1. Launch the Veeam ONE Settings utility available under the following path:

    C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

  2. In the menu on the left, select General, open the Database tab and make the necessary changes in the SQL Server section.
    User-added image

  3. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for performance data collection.

  4. Click the Test Connection button to check whether new configuration settings are correct.

  5. Save changes.

  6. Restart Veeam ONE Monitor Server service.

Then modify connection settings for Veeam ONE Reporter and Business View. To accomplish that, follow the next steps:

  1. In the list of services, locate Veeam ONE Reporter Server service and choose to modify its properties. Open the Log On tab and specify the necessary account for the service in the Log on as section.

  2. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for data collection.

  3. Launch the Veeam ONE Settings utility available under the following path:

    C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

  4. In the menu on the left, select General, open the Web Identity tab and make the necessary changes in the Web identity section.
    User-added image

  5. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for overall Web UI operation and reports creation.

  6. Save changes.

  7. Restart Veeam ONE Reporter Server service.

 

IMPORTANT!

  • Should the database be connected to a different Veeam One installation, make sure there is no version\build mismatch. Otherwise, the application will fail.
  • Starting with Veeam One v8, database partitioning became an option. If this option has been in place on the previously used SQL server, follow the steps described in this KB article to implement it on the new SQL server. 
  • Starting with Veeam One v9.5, index defragmentation maintenance job for Veeam One database has been implemented. To create this job on the new SQL server download and run this script.

NOTE
Veeam One database partitioning jobs (VeeamOneSqlMaintenance_Med and VeeamOneSqlMaintenance_Med) and index defragmentation maintenance job (VeeamOne Maintenance Job) will remain intact on the old SQL server under SQL Server Agent > Jobs node and need to be removed manually.

More Information

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

HCL Tape - Quantum Scalar i6000

$
0
0

Challenge

Product Information:

Product Family: Scalar Tape Devices 
Status: Veeam Ready - Tape 
Classification Description: Tape device where available hardware features have been tested to work with Veeam. 

Solution

Product Details:

Model number: i6000 
Library firmware version: i12.4.2 – 736Q.GS00500 
Drive firmware version: IBM LTO7 G5S0 
Driver for tape drive: 6.2.5.8 
Driver for media changer: 6.2.5.8 
General product family overview: Scalar libraries are the intelligent choice for archiving applications and long-term data retention. Proactive and automated monitoring and management reduces administration time and service interruptions keeping IT staff focused on key business objectives. With ease of management, industry leading performance, reliability and scalability, it’s easy to see why Quantum is the market share leader in tape backup and automation. 


Veeam Details

Veeam Build Number: 9.0.0.1715

More Information

Company Information

Company name: Quantum 
Company overview: Quantum is a leading expert in scale-out storage, archive and data protection, providing intelligent solutions for capturing, sharing and preserving digital assets over the entire data lifecycle. We help customers maximize the value of these assets to achieve their goals, whether it’s top movie studios looking to create the next blockbuster, researchers working to accelerate scientific discovery, or small businesses trying to streamline their operations. With a comprehensive portfolio of best-in-class disk, tape and software solutions for physical, virtual and cloud environments, we enable customers to address their most demanding workflow challenges and opportunities.

HCL Tape - Quantum Scalar i500

$
0
0

Challenge

Product Information

Product Family: Scalar Tape Devices 
Status: Veeam Ready - Tape 
Classification Description: Tape device where available hardware features have been tested to work with Veeam.

Solution

Product Details

Model number: i500 
Library firmware version: i8.5.1-681G.GS002 
Drive firmware version: IBM LTO7 G340 
Driver for tape drive: 6.2.5.8 
Driver for media changer: 6.2.5.8 
General product family overview: Scalar libraries are the intelligent choice for archiving applications and long-term data retention. Proactive and automated monitoring and management reduces administration time and service interruptions keeping IT staff focused on key business objectives. With ease of management, industry leading performance, reliability and scalability, it’s easy to see why Quantum is the market share leader in tape backup and automation. 

 

Veeam Details

Veeam Build Number: 9.0.0.1715

More Information

Company Information

Company name: Quantum 
Company overview: Quantum is a leading expert in scale-out storage, archive and data protection, providing intelligent solutions for capturing, sharing and preserving digital assets over the entire data lifecycle. We help customers maximize the value of these assets to achieve their goals, whether it’s top movie studios looking to create the next blockbuster, researchers working to accelerate scientific discovery, or small businesses trying to streamline their operations. With a comprehensive portfolio of best-in-class disk, tape and software solutions for physical, virtual and cloud environments, we enable customers to address their most demanding workflow challenges and opportunities.


HCL Tape - Quantum Scalar i3 i6

$
0
0

Challenge

Product Information

Product Family: Scalar Tape Devices 
Status: Veeam Ready - Tape 
Classification Description: Tape device where available hardware features have been tested to work with Veeam.

Solution

Product Details

Model number: i3 and i6 
Library firmware version: 11OG.TS121 
Drive firmware version: IBM LTO7 HH G5S1; IBM LTO7 FH G9Q0 
Driver for tape drive: 6.2.5.8 
Driver for media changer: 6.2.5.8 
General product family overview: Scalar libraries are the intelligent choice for archiving applications and long-term data retention. Proactive and automated monitoring and management reduces administration time and service interruptions keeping IT staff focused on key business objectives. With ease of management, industry leading performance, reliability and scalability, it’s easy to see why Quantum is the market share leader in tape backup and automation. 


Veeam Details

Veeam Build Number: 9.0.0.1715

More Information

Company Information

Company name: Quantum 
Company overview: Quantum is a leading expert in scale-out storage, archive and data protection, providing intelligent solutions for capturing, sharing and preserving digital assets over the entire data lifecycle. We help customers maximize the value of these assets to achieve their goals, whether it’s top movie studios looking to create the next blockbuster, researchers working to accelerate scientific discovery, or small businesses trying to streamline their operations. With a comprehensive portfolio of best-in-class disk, tape and software solutions for physical, virtual and cloud environments, we enable customers to address their most demanding workflow challenges and opportunities.

HCL Tape - IBM TS3500

$
0
0

Challenge

Product Information

Product Family: IBM Midrange Tape Library 
Status: Veeam Ready - Tape 
Classification Description: Tape device where available hardware features have been tested to work with Veeam.

Solution

Product Details

Model number: TS3500 
Library firmware version: F030 
Drive firmware version: F980 
Driver for tape drive: 6.2.5.8 
Driver for media changer: 6.2.5.8 
General product family overview: IBM® TS3500 Tape Library is designed to provide a highly-scalable, automated tape library for mainframe and open-systems backup and archive that can scale from midsized to large enterprise environments. 

 

Veeam Details

Veeam Build Number: 9.0.0.1715

More Information

Company Information

Company name: IBM 
Company overview: IBM is the worldwide tape market share leader offering a full range of tape storage solutions including drives, autoloaders, libraries, virtual tape systems and Spectrum Archive software which can make tape as easy to use as disk. 

HCL - StoreOnce with Catalyst

$
0
0

Challenge

Product Information:

Product Family: HPE StoreOnce w/Catalyst
Status: Veeam Ready – Integrated; Veeam Ready - Repository 
Classification Description: Integrated storage where joint development activities between the manufacturer and Veeam have occurred to create advanced backup and restore functionalities. This device can support all Veeam backup and restore features.   

Solution

Product Details:

Model number: All StoreOnce Models
Firmware version: 3.13.1-1546.2 or later (3.15.1-1636.1 or later required for vPower features)
General product family overview: From ROBO to the entire enterprise, HPE StoreOnce System with HPE StoreOnce Catalyst is a single and agile backup and recovery solution. Reduce costs and keep pace with rapid data growth, confident that your SLAs are securely met.


Veeam Details:

Veeam Build Number: 9.0.0.902
Veeam Settings:

  • Repository Type: Deduplicating Storage Appliance
  • Deduplication: OFF
  • Compression: Optimal
  • Storage Optimization: Local target (16TB+ backup files)
  • Per-VM Backup Files: ON
  • Decompress before storing: ON
  • Align backup file blocks: OFF

More Information

Special Considerations:

HPE StoreOnce with Catalyst is recommended as a secondary backup target for long-term retention of Veeam backup files.

Company Information:

Company name: Hewlett Packard Enterprise
Company overview: HPE delivers high-quality, high-value products, consulting, and support services in a single package. That’s one of their principal differentiators. They have industry-leading positions in servers, storage, wired and wireless networking, converged systems, software, services and cloud.

HCL - Exagrid with Data Mover

$
0
0

Challenge

Product Information:

Product Family: ExaGrid with Veeam Accelerated Data Mover
Status: Veeam Ready - Integrated; Veeam Ready - Repository
Classification Description: Integrated storage where joint development activities between the manufacturer and Veeam have occurred to create advanced backup and restore functionalities. This device can support all Veeam backup and restore features.  

Solution

Product Details:

Model number: All EX Series Models
Firmware version: 4.7, 4.8
General product family overview: ExaGrid understands that deduplication is required, but how you implement it changes everything in backup. ExaGrid has a unique landing zone where backups can land straight to disk without any inline processing. Backups are fast and the backup window is short. Deduplication and offsite replication occur in parallel with the backups. Deduplication and replication never impede the backup process as they always are second order priority. ExaGrid calls this “adaptive deduplication.”

 

Veeam Details:

Veeam Build Number: 9.0.0.902
Veeam Settings:

  • Repository Type: Deduplicating Storage Appliance
  • Deduplication: ON
  • Compression: Dedupe-friendly
  • Storage Optimization: Local target
  • Per-VM Backup Files: ON
  • Decompress before storing: OFF
  • Align backup file blocks: OFF

More Information

Special Considerations:

Scale-out Backup Repositories aren’t currently supported on ExaGrid EX series appliances.


Company Information:

Company name: ExaGrid
Company overview: ExaGrid is a recognized visionary, innovator, and leader in the disk-based backup storage space. ExaGrid takes a unique approach to backup by addressing all the requirements of backup performance, restores performance, backup window length, disaster recovery, and cost up front and over time.

HCL - Oracle ZFS

$
0
0

Challenge

Product Information

Product Family: Oracle ZFS 
Status: Veeam Ready - Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features.   

Solution

Product Details

Model number: Oracle ZFS Storage Appliance 
Number of Drives: 38 – 7.2k HDD, 2 - SSD for write cache, 1 - SSD for read cache 
Firmware version: OS 8.6.x 
Additional support: Any hardware configuration with an equal or greater hardware configuration 
General product family overview: Oracle ZFS Storage Appliance architecture is powered by a multithreaded SMP operating system with massive DRAM caches that can immediately serve 70 to 90 IOs, enabling applications to respond immediately to your queries or your customer’s transactions. Because of its fast responsiveness, the Oracle ZFS Storage Appliance can be used in cloud environments or on premises for a variety of demanding workloads including business analytics and data warehouses, DevTest, data protection and virtualization. 

 

Veeam Details

Veeam Build Number:  9.0.0.902
Veeam Settings:  

  • Repository Type: Windows 
  • Deduplication: Enabled 
  • 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: Oracle Inc., America 
Company overview: Oracle offers a plethora of applications, databases, servers, storage and cloud technologies to empower modern business. We provide a wide array of software, systems and cloud deployment models – including public, on-premises and hybrid clouds to ensure that the technology flexes to the unique needs of a business.

Unable to install Backup Enterprise Manager

$
0
0

Challenge

Attempting to install Backup Enterprise Manager results in a ‘fail’ during port selection, with the specified HTTPS Port being unavailable.

User-added image

Cause

The port is already consumed by the World Wide Web Publishing Service

Solution

Disable the World Wide Web Publishing Service, proceed with the installation, then re-enable the service.

Upgrade to Veeam Backup & Replication 9.5 fails with "Unsupported SQL Version"

$
0
0

Challenge

Upgrade to Veeam Backup & Replication 9.5 you receive the error "Unsupported SQL Version"

Cause

If you have a supported database (2008 or newer), the upgrade cannot be installed if the compatibility mode is set to 2005.

Solution

Manually update the compatibility of the VeeamBackup database (or custom named equivalent) via SQL Management Studio or using a query. The compatibility mode must be set to 2008 or newer.

Query:
Alter Database VeeamBackup set compatibility_level = 100

UI:
1. Connect to instance via SSMS
2. Right-click Veeam Database -> Properties
3. Select Options
4. Select Compatibility Level
5. Set to 2008, 2012, 2014 or 2016.

How to: Collect Information Necessary for Cloud Connect Technical Support Cases

$
0
0

Challenge

Given the additional complexity of Cloud Connect compared with standalone installations of Backup & Replication, additional logging and information is needed to expedite cases with our Cloud Connect teams whenever feasible. All information should be obtained whether you are submitting an issue as a Veeam Cloud Connect Tenant or a Veeam Cloud Connect Provider.

Solution

Necessary Infrastructure Information

If not already included in case submission:

  • Provider Name:
  • Tenant Name:
  • Job Type that is having issues:
  • Job Name that is having issues:
  • Tenant Public IP:
*Please document the public IP of the Tenant Veeam Server connected to the cloud gateway. This is used to identify the connection in the Cloud Gateway logs.
You can identify this by using a utility such as http://www.whatsmyip.org/

 

Tenant Logging

If not already included in case submission:

Please reproduce the error (if applicable), collect and submit tenant logs for the job as you would any standard Backup & Replication case using the instructions below:
https://www.veeam.com/kb1832


Collecting Logs from Tenant Environment

For failing jobs:
Export logs for the job (backup, backup copy, or replication) that is having an issue.


User-added image
 

For restores and replica failovers:
Export a log bundle for the backup or replication job (as above), and then manually collect the following directories from the Veeam Backup server.

Starting in %ProgramData%\Veeam\Backup\:
  • Entire directory "CloudConnect" (if it exists)
  • Entire directory with the name of the VM that was backed up or replicated

 

Service Provider Logging

If not already included in case submission:

After reproducing the error (if applicable), collect and submit provider logs for the job using the instructions below:
 

Collecting Logs from Service Provider Environment
 
For providers with newly-configured infrastructure, or a small number of clients, use the built-in log generator tool to gather logs from all managed servers related to the issue. It is important to gather logs from cloud gateways, repositories, and other relevant infrastructure in addition to the backup server.

User-added image
 

Please make sure to specify the component logs for all servers and specify only the last 2-3 days.

Providers with a larger number of clients can use this tool, but it will produce a large (multi-GB) log bundle. To avoid this, see “Advanced Service Provider Location”, below.



Advanced Service Provider Location
 
Some files listed may not be present if they are not applicable to your issue, but make sure you are looking at the correct server for each different directory or filename. Some files will have several rotations, with the oldest files archived to .zip or .gz.

Veeam Backup and Replication Server:
Collect these files in the root of %ProgramData%\Veeam\Backup\: 
  • Svc.VeeamBackup* (filenames beginning with “Svc.VeeamBackup”)
  • Zip files named "<date stamp>_Svc.VeeamBackup"
  • CloudAppliance*
  • In rare cases, other files in this directory may be relevant, so it is prudent to include anything with a recent modified date.
 
Collect the contents of these folders:
  • %ProgramData%\Veeam\Backup\Console\ (if using remote console, collect from that machine as well)
  • %ProgramData%\Veeam\Backup\CloudConnect\
  • %ProgramData%\Veeam\Backup\CloudConnectService\<tenant_name>\
  • %ProgramData%\Veeam\Backup\CloudConnectService\ (excluding subfolders for other tenants)

Cloud Gateway Servers:
  •  %ProgramData%\Veeam\Backup\Svc.VeeamGateSvc*
     
WAN Accelerator (if applicable):
  • %ProgramData%\Veeam\Backup\Svc.VeeamWANSvc*.log
     
Repository Servers (for backup and backup copy jobs):
Check which server is listed as the Host for the Repository in the console: Backup Infrastructure > Backup Repositories. Collect the entire content of these folders:

 
Windows:
  • %ProgramData%\Veeam\Backup\CloudConnectService\<tenant_name>\
  • %ProgramData%\Veeam\Backup\CloudConnectService\ (excluding subfolders for other tenants)
 
Linux:
  • /var/log/VeeamBackup/CloudConnectService_<tenant_name>_* (may be multiple directories)
It’s best to save this information to a .zip file with an identifiable name such as "<tenant_name>-ProviderLogs.zip"

More Information

Logs from the Network Extension Appliances are automatically copied to their controlling Veeam Backup & Replication server, so in most cases it is not necessary to gather logging from these appliances manually.

Be sure to alert your engineer if you have issues with being able to contact your provider or obtain this logging in any way so we can assist

Space Requirements for Backup Copy Jobs

$
0
0

Challenge

Storage space is a concern for backup copy jobs in Veeam. If the repository is insufficiently provisioned, retention can fail, leading to the repository filling up and the job failing. If this happens, the job must often be restarted from scratch.

Cause

First and most important to note is that backup copy job retention happens differently from local backups. As a copy job is optimized for off-site storage, we assume there may be connection issues over a WAN that aren’t present on a LAN. Merges, as a result, are done via temp file, instead of writing the VIB incremental data directly into the VBK full.
 
This temp file is going to be as big as (if not slightly larger than, due to changing data) the VBK. Once the merge is complete, the VIB and the old VBK are deleted and the temp file takes their place.
 
For GFS retention, every Weekly, Monthly, Quarterly, and Yearly backup is itself a VBK, and of similar size.

Solution

To estimate the space requirements for a backup copy job:
 

  • Add the sizes of a full backup of all local jobs that will be included in the copy job. You may end up with a slightly smaller copy job due to compression and deduplication of similar blocks, but it’s preferable to plan for more.

  • Determine how many full backups you’ll have:

    • One full for the regular retention

    • One full for every Weekly, Monthly, Quarterly, and Yearly GFS archival point

  • Add one more point to the total for the temp file used in the merge process

  • Multiply that total by the size estimate for the full backup. Ensure your repository will have space for at least this much data, and a bit more for incrementals/variance in data.

 
Example:
 
Consider two local backup jobs being written to a single backup copy job. A full backup of the first job is around 750GB and a full backup of the second is 500GB. Add the two together. 1.25TB should be accounted for the combined full of the copy job, and a minimum of another 1.25TB should be allowed for the merge.
 
The same two local backup jobs have a combined daily rate of change of 170GB (Local Backup 1, on a given week, has increments sized 100, 120, 100, 150, 125, and 175GB for an average of 128.334~ and Local Backup 2 has increments of 50, 40, 55, 30, 45, and 30GB for an average of 41.667). If the backup copy job will retain 14 points, allow at minimum 14 * 170GB or 2.38TB for increments. Given that one cannot consistently predict rates of change, it’s best to oversize here rather than to be left wanting.
 
Assuming no GFS retention on this example job, the backup copy repository should have:
 
[1.25TB (full)] + [1.25TB (merge overhead)] + [2.38TB (incremental points)] = 4.88TB
 
If we add GFS retention of 4 monthly points, those four full restore points add 4 * 1.25TB = 5.0TB. In this case we would need:
 
[1.25TB (full)] + [5.0TB (GFS points)] + [1.25TB (merge overhead)] + [2.38TB (incremental points)] = 9.88TB
 
As a general rule, a bit of additional space is recommended for unforeseen issues. Insufficient sizing for a merge can lead to running out of space, and if a copy job repository ends up with insufficient space to perform a merge—and subsequently is filled with more increments than specified by retention—the only recourse in almost every case is to clear the repository and let the copy job start with a new full, or provision more space for the repository if it is scalable.

Upgrade fails with “Unable to use database VeeamBackup, because it has an unsupported compatibility level (SQL Server 2008 or later is required)”

$
0
0

Challenge

When attempting to upgrade the Veeam Backup and Replication software, an error is encountered:

Unable to use database VeeamBackup, because it has an unsupported compatibility level (SQL Server 2008 or later is required)
 

Cause

Veeam Backup and Replication 9.5 no longer supports databases with a compatibility level of 2005 or lower.
 

Solution

Change the compatibility level of the database to 2008 or higher:

In SQL Server Management studio this can be done by following these steps:
  1. Right-click the database in question
  2. Click ‘properties’ 
  3. Click the ‘options’ tab 
  4. Drop down the ‘Compatibility Level’ box and change the compatibility level to 2008 or higher
User-added image

The following queries can be run to check the compatibility level and change it:

(Before running any queries, always back up the Veeam database (http://www.veeam.com/kb1471))
To check the compatibility level run:
 
SELECT compatibility_level 
FROM sys.databases WHERE name = 'Veeambackup';  

 
To change the compatibility level run***:
 
ALTER DATABASE Veeambackup
SET COMPATIBILITY_LEVEL = 100;

 
***‘100’ is the compatibility level for 2008. To change it to 2012, use ‘110’. To change it to 2014, use ‘120’. You cannot change the compatibility level to be high than the version of the SQL instance being used.
 

Exporting Veeam Endpoint backups as virtual hard disk files

$
0
0

Challenge

Veeam Endpoint Backup can be used to export the backed up drives of a physical workstation by converting the backup files to a virtual hard drive file with the help of Veeam Backup and Replication. Though it is possible, improper implementation may result in driver-­related BSOD on the new VM and other issues.

The purpose of this article is to minimize the likelihood of issues related to the export.

Cause

There are a number of possible issues that manifest themselves when using Veeam Endpoint Backup this way, such as copied IDs, incompatible drivers etc. 

Solution

The approach described below cannot be regarded as a fully operational physical-to-virtual conversion. Rather, it is a description of the recommended way of exporting the backed up drives of a physical machine so they can be used in a virtual environment.

Scenario 1: you need to use the backed up drives of a physical workstation in one virtual machine. The original machine will be decommissioned afterwards, no clones of the machine will be created.

If you need to export the backed up drives of one specific workstation without deploying it to multiple VMs, you can follow this scenario:
  1. Create recovery media image (ISO) as described here.
  2. Create a backup of your system with Veeam Endpoint Backup.
  3. Boot the virtual machine with the recovery image you created in step 1 as described here.
  • Make sure that the option to "Inject these drivers into operating system while performing bare metal recovery" is checked.
  • Use the backup you created in step 2 to restore your original workstation.
Be advised, that the first job after the successful export will create another full backup, but the original backup chain will resume.

Scenario 2: you need to use the backed up drives to deploy multiple machines.

If you need to deploy an image to more than one machine with Endpoint pre-­installed and pre-­configured, use this article

More Information

Important MS Windows licensing notice.

The MS Windows activation is usually linked to the motherboard and CPU. Once the hardware is changed, re-activation may be required.

In case you are using OEM MS Windows license, keep in mind, that the OEM license is only valid for a single piece of hardware and will not work on a different workstation.

Tape Jobs fail with I/O errors or (SCSI) Bus resets

$
0
0

Challenge

Failures occur during the File to tape or Backup to tape jobs. The jobname.log shows error messages similar to:
 
"error: The request could not be performed because of an I/O device error"
"error: Tape fatal error.\nThe I/O bus was reset"

Cause

Depending on the type of connection, controller or library used, periodic status requests may be handled too slow and fill up the queue. As a result, Windows may try to recover by resetting the bus.

Solution

For Veeam B&R v7.x:
 
1. Increase the time between status requests by adding following registry entry, and restart the Veeam services:
HKLM\Software\Veeam\Veeam Backup and Replication - create a DWORD "TapeDeviceWatcherTimeoutSec" with a value "300"

2. Additionally you may need to increase storport timeouts by creating a "StorPort" key with entries for all tape devices: HKLM\System\CurrentControlSet\Enum\SCSI\DEVICEID\INSTANCE\DeviceParameters\StorPort\

You can get DEVICEID & INSTANCE with the following PowerShell command: gwmi -class win32_tapedrive

- create a DWORD "BusyRetryCount" with the value "1000"
- create a DWORD "BusyPauseTime" with the value "1000"
- create a DWORD "BusyTimeoutCount" with the value "5000"

3. Reboot the server, for StorPort settings to be applied

For Veeam B&R v8.x or v9.x:
 
1.Increase storport timeouts by creating a "StorPort" key on the tape server  with entries for all tape devices: HKLM\System\CurrentControlSet\Enum\SCSI\DEVICEID\INSTANCE\DeviceParameters\StorPort\

You can get 
DEVICEID & INSTANCE with the following PowerShell command: gwmi -class win32_tapedrive

- create a DWORD "BusyRetryCount" with the value "1000"
- create a DWORD "BusyPauseTime" with the value "1000"

- create a DWORD "BusyTimeoutCount" with the value "5000"

2. Reboot the tape server, for StorPort settings to be applied
Viewing all 4469 articles
Browse latest View live


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