↧
Application is Shutting Down
↧
Hyper-V Guest processing skipped (check guest OS VSS state and integration components version)
↧
↧
All tape write operations fail for MHVTL if the block size on drives differs from 65 KB
Challenge
All tape write operations fail for MHVTL if the block size on drives differs from 65 KBCause
Veeam Backup & Replication v9 has a new algorithm of choosing the block size. Now Veeam automatically detects the highest available block size and runs jobs according to this value. Currently this option is available for all supported devices except MHVTL.Solution
Manually change the block size in this dialog box:More Information
Please see Data Block Size section here↧
SQL Server Transaction logs do not match any existing database backup: [DB Name]
Challenge
You have a Periodic SQL Logs Backup within a Backup Job. You receive the following error:"Collected SQL Server transaction logs do not match any existing database backup: [DB Name]”
Cause
The Periodic SQL Log Backup does not have a Full backup to reference.Solution
Start the Backup Job (right click the job > Start).This will provide a Full SQL backup for the Transaction log backup to reference.
More Information
Please Note:- Native SQL Backups cannot be taken in conjunction with Veeam SQL Log backups unless they are COPY ONLY. Multiple applications interacting with the Transaction logs will break the consistency and prevent proper restores.
For a Visual Guide on how to stop SQL Transaction Log Backup Job:
↧
How to Change or Move the Web Site URL in BEM
Challenge
You need the process on how to change or move the Web Site URL in Veeam Backup Enterprise Manager.
If you change the server host name that is running IIS, move the Veeam Backup Enterprise Manager (BEM) Database to a new server with the old DB. Changes between the new Backup Enterprise Manager installation (IIS) and the old Database may result in emails being delivered incorrectly to the old Backup Enterprise Manager server.
Solution
To fix your issue:
- Please create a backup of your VeeamBackupReporting database using the following KB:
www.veeam.com/kb1471 - Open Microsoft SQL Server Management Studio for the Backup Enterprise Manager SQL database. If you are using the express version of SQL, this may need to be downloaded and installed to edit SQL correctly.
- Open the Management Studio and go to "ConnectedServer\InstanceName" --> Databases --> VeeamBackupReporting --> Tables --> dbo.Notification.MailSettings.
- Once here, you can either select "Edit top 200 Rows" or "Open Table" to edit this table.
- In the column "web_site_url", look for the website listed as https://YOUR_OLD_SERVER_NAME:9443/default.aspx and change it to https://YOUR_NEW_SERVER_NAME:9443/default.aspx .
- Restart Veeam Backup Enterprise Manager service in services.msc
More Information
The "dbo.Notification.MailSettings" Table in the SQL Database "VeeamBackupReporter" contains more important information that cannot be edited with the Veeam Backup Enterprise Manager itself. This includes the body of the email message. Everything else should be editable within Veeam Backup Enterprise Manager under Backup Enterprise Manager --> Configuration --> Notification.
↧
↧
Failed to load jet library
Challenge
The following error occurs when attempting to perform a restore using Veeam Explorer for Exchange:“Failed to load jet library from C:\ProgramData\Veeam\Backup\ExchangeExplorer\ESE\V15\ese.dll”
Solution
To solve, upgrade to Internet Explorer 10+ as it contains the necessary Windows files to leverage the ese.dll correctly for the restore.More Information
If Internet Explorer 10+ is already installed on the Veeam Backup and Replication server, in programs and Features verify Microsoft Visual C++ 2008 Redistributable Package (X64) is installed along with Microsoft Visual C++ 2010 Redistributable Package (X64). If it is not installed please use the link below to install it on the Veeam Backup and Replication server.https://www.microsoft.com/en-us/download/details.aspx?id=15336
↧
How to Use the Veeam Backup Validator
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)
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
↧
SQL VSS Writer is missing: databases will be backed up in crash-consistent state and transaction log processing will be skipped
Challenge
Job reports warning "SQL VSS Writer is missing: databases will be backed up in crash-consistent state and transaction log processing will be skipped"Running vssadmin list writers shows that SqlServerWriter in not in the list.
Cause
There are different causes of the issue:- the SQL instance have databases with names ending in a space character.
- the account under which SQL VSS Writer service is running doesn't have sysadmin role on a SQL server
- SQL VSS Writer service stuck in an invalid state
Solution
Depending on a particular cause:- Please rename the database to a new name (without a space in it)
- Grant the SQL VSS Writer service user a sysadmin role (Instructions in KB here here: https://www.veeam.com/kb1978)
- Restart SQL VSS Writer service (Instructions in KB here herehttps://www.veeam.com/kb2041)
- In the case of SBS machines that are also Domain Controllers, ensure that the SQL Writer is running as a domain administrator and not local system
↧
“Server Error in '/' Application” After Installing/Upgrading Backup Enterprise Manager
Challenge
After installing or upgrading Veeam Backup Enterprise Manager, the following error occurs:
“Server Error in '/' Application”
Could not load file or assembly 'Veeam.Backup.Common' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Could not load file or assembly 'Veeam.Backup.Common' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Cause
Veeam Backup Enterprise Manager has not been upgraded correctly or ASP is running a 32 bit version when it should be running a 64bit version.Solution
To resolve, reinstall Veeam Backup Enterprise Manager or force ASP to run in 64bit mode.NOTE: If this error occurs after an upgrade of the software, please reinstall the Backup Enterprise Manager.
If this error appears from a fresh install of the Backup Enterprise Manager, please follow the troubleshooting below to try and resolve the issue.
After installing Veeam Enterprise Manager, you try to access it via the URL and you get an error having to do with Veeam.Common application error. The issue here is that IIS is running a 32bit version of ASP and it needs to be forced to 64bit, which can be done using the following MS Knowledgebase. After running the two commands below in step #3 and #4 you can simply open Backup Enterprise Manager and you will get the login screen successfully.
http://support.microsoft.com/kb/894435
To run the 64-bit version of ASP.NET 2.0, follow these steps:
1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to disable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
3. Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
4. Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager.
5. Try to log into the Backup Enterprise Manager to test to see if it now works OK.
For IIS 7 please follow these steps:
- In IIS manager, select “Application Pools".
- Right click the “VeeamBackup”, choose “Advanced settings”.
- You will see the “Enable 32-bit Application” option under “General”. Change it from True to False.
Select the VeeamBackup Application Pool>Advanced Settings>Load User Profile: Enable True
↧
↧
SQL Deadlock log collection
Challenge
To gather logs for SQL Deadlock troubleshooting.Cause
DB actions can in certain circumstances cause deadlock issues.Solution
Please ensure that you have SQL Server Management Studio Tools (SSMS) installed on the Veeam computer. http://www.veeam.com/kb1761 references where to download SSMS. Install the most recent version as it is backward compatible with older versions of SQL while older instances of SSMS are not compatible with newer versions of SQL.For SQL versions 2012+:
1. Connect to the Veeam SQL DB. The default connection parameter for Veeam Backup and Replication version 8 and 9 is localhost\VEEAMSQL2012.
2. Expand Management > Extended Events > Sessions > System health
3. Right click package0.event_file and select "View Target Data"
4. Select "Filters..."
5. Click on "click here to add a clause" then enter the values as listed below:
Field = name, Operator = Contains, Value = deadlock
6. Click "Apply", then click "OK"
7. Right-click the most recent deadlock and select "Copy > Details"
8. Send a copy of the resulting data Veeam support
For SQL versions before 2012:
1. Connect to the Veeam SQL DB
The default connection parameter for Veeam Backup and Replication version 8 and 9 is localhost\VEEAMSQL2012.
2. Run the following query on the Veeam database, "DBCC TRACEON (1222, -1)".
3. Recreate the errors in Backup and Replication.
4. Collect all “ERRORLOG” files from the MS SQL server instance
By default the SQL instance logs are on the Veeam computer with the path “C:\Program Files\Microsoft SQL Server\MSSQL10_50.VEEAMSQL2008R2\MSSQL\Log”.
5. Generate a backup of the Veeam database as per https://www.veeam.com/kb1471
6. Generate a Veeam log bundle as per https://www.veeam.com/kb1832
7. Send the database errors logs, database backup, and Veeam logs to Veeam support for review
↧
Error timed out requesting agent ports for client session. failed to initialize agent during a backup.
Challenge
The Veeam Endpoint Backup job fails with the error message:Error AgentManagerService: Failed to start agent, Host <name of computer>
The host name is the local machine from which Veeam Endpoint Backup is installed on. In the logs the following additional error message may show up.
Error --tr:Failed to initialize agent ( specified agent path: [C:\Program Files\Veeam\Endpoint Backup\x86\VeeamAgent.exe], arguments: [ -g"2500-5000" -i"{3809193f-46f6-4fcc-b001-bfc8aad51678}" -l"flush,C:\ProgramData\Veeam\Endpoint\Backup__Job__PRIMACYDC/Agent.Backup__Job__PRIMACYDC.Source.PRIMACYDC.log" -f 25 --vddkLogLevel 1 --maxPendingBlocks 10000 -n -x"{f7bb330c-50e4-4f50-8f69-851aa0a243ee}"])
When attempting to manually start the veeamagent.exe from the specified agent path, the following windows message comes up:
The program can’t start because dbghelp.dll is missing from your computer. Try reinstalling the program to fix the problem.
Cause
This means that the Veeam Agent is not starting up because there is some corruption on the computer’s file system.Solution
To resolve:1. Run full computer scan with anti-virus software.
2. Open up the command prompt as an administrator and run sfc /scannow. It should locate any issues with the file system or registry and fix them.
More Information
Note that re-installation of Veeam Endpoint Backup may be needed after completion of the steps above.↧
Failed to truncate transaction logs for SQL instances on Shared VHDX
Challenge
When attempting to run a backup job for a SQL Server that is in either a SQL Server Failover Cluster or AlwaysOn Failover Cluster with a shared VHDX the backup job reports the warning:“Failed to truncate transaction logs for SQL instances: <>. Possible reasons: lack of permissions, or transaction log corruption” or SQL log backup job fails with “Regular database <> was not backed up in Oib”
On the guest, within the VeeamGuestHelper.log found in %programdata%\Veeam\Backup the following line can be found:
OLEDB Error: 'BACKUP LOG cannot be performed because there is no current database backup.'
Cause
This is behavior by design. Backup of VMs with shared VHDX disks can only be performed in crash consistent mode, with Application-Aware Procesing disabled.
Because the VSS subsystem is not involved in the backup process, the SQL Server is not aware of a backup having occurred and does not update date of last database backup. Due to this lack of an update to the last database backup entry, when the SQL Instances receives the command to truncate logs (“backup log”), it cannot find a corresponding database backup event and returns the error above.
Solution
SQL logs truncation or backup is not possible in this configuration. Please change to using a AlwaysOn Availability Groups SQL installation with individual VHD(X) for each VM.More Information
Please see the Release Notes for details:https://www.veeam.com/ru/documentation-guides-datasheets.html
↧
How to use DiskSpd to simulate Veeam Backup & Replication disk actions
Challenge
The test file created by these tests do not contain any diagnostic information and will need to be manually removed after testing has concluded. All diagnostic information regarding the performance results are displayed in the command line. Please do not send the testfile.dat into support, its contents will not help with troubleshooting.This document contains information on how to use Microsoft© DiskSpd to simulate Veeam Backup & Replication disk actions to measure disk performance.
DiskSpd can be found here: https://gallery.technet.microsoft.com/DiskSpd-a-robust-storage-6cd2f223
Solution
Below are some details on the options and some simulations you can do to measure disk speed independently of Veeam. Please keep in mind as with all synthetic benchmarks real-world results may differ.──────────────────────────────────────────────────────────
Common parameters
──────────────────────────────────────────────────────────Usage: diskspd [options] target1 [ target2 [ target3 ...] ]
Target
Available targets:
· File on a volume with an assigned letter: D:\testfile.dat
· File on a CIFS/SMB share: \\nas\share\testfile.dat
· File on an NFS share, provided you have mounted it to a disk letter with Client for NFS: N:\testfile.dat
· Disk: #X where X is the number of the disk in Disk Management. You can use a local disk or one attached by iSCSI, and it does not matter if they are Online are Offline. In this mode diskspd reads or writes directly from/to the disk ("RAW").
You can specify multiple targets. This way you can simulate several jobs running at the same time.
Block size
-b specifies the size of a read or write operation.
For Veeam, this size depends on the job settings. By default, "Local" storage optimization setting is selected and this corresponds to 1MB block size in backups. However, every block of data is compressed (unless using the Decompress option) before it is written to the backup file, so the size is reduced. It is safe to assume that blocks compress on average down to half the size, so in most cases picking a 512KB block size is a good estimate.
If the job is using a different setting, WAN (256KB), LAN (512KB) or Local+ (8MB), change the -b value accordingly to 128KB, 256KB or 4MB. And if the Decompress option is on don't halve the values.
File size
-c specifies the file size you need to create for testing. Typically 1 GB should be enough. Anything lower can be easily cached by hardware and thus yield incorrect results.
Duration
-d specifies the duration of the test. By default it does 5 seconds of warm up (statistics are not collected), then 10 seconds of the test. This is OK for a short test, but for more conclusive results run the test for at least 10 minutes (-d600).
Caching
-h disables Windows and hardware caching.
This flag should always be set. VeeamAgents always explicitly disable caching for I/O operations for greater reliability, even though this results in lower speed. Windows Explorer for example, does use the Cache Manager and in a very simple copy-paste test will get greater speeds than Veeam does, due to cached reads and lazy writes. That is why using Explorer is never a valid test.
──────────────────────────────────────────────────────────
Active full or forward incremental
C:\diskspd> diskspd.exe -c1G -b512K -w100 -h -d600 D:\testfile.dat
-w100 indicates 100% writes and 0% reads. Sequential I/O is used by default.
IMPORTANT: Contents of testfile.dat will be destroyed without a warning.
──────────────────────────────────────────────────────────
Reverse incremental
Reverse incremental
C:\diskspd> diskspd.exe -c1G -b512K -w67 -r4K -h -d600 D:\testfile.dat
-w67 indicates 67% writes and 33% reads to simulate 2 write and 1 read operations that happen in reverse incremental backup jobs.
-r4K enables random I/O that are 4KB aligned, for a more realistic simulation.
IMPORTANT: Contents of testfile.dat will be destroyed without a warning.
After the test has finished, take Total IO MB/s from the results and divide it by 3. This is because for every processed block Veeam needs to do 3 I/O operations, thus the effective speed is 3 times slower.
──────────────────────────────────────────────────────────
Transforms, merges, and other synthetic operations
Includes transformation of incrementals to rollbacks, merge operations in forever forward incremental backups and backup copy jobs, and creation of synthetic full backup files and GFS points.
C:\diskspd> diskspd.exe -c1G -b512K -w50 -r4K -h -d600 D:\testfile.dat
-w50 indicates 50% writes and 50% reads to simulate reading data from one file and writing that data into another (or in the case of transform, reading the same number of blocks from two files as are written to two other files).
-r4K enables random I/O that are 4KB aligned, for a more realistic simulation.
IMPORTANT: Contents of testfile.dat will be destroyed without a warning.
After the test has finished, take Total IO MB/s from the results and divide it by 2 (4 for transform to rollbacks). This is because for every processed block Veeam needs to do 2 I/O operations, thus the effective speed is 2 times slower. For transform to rollbacks, each block must be read out of the full backup file and written into the rollback before the corresponding block can be read out of the incremental and written into the full, which results in 4x I/O.
To estimate an expected time to complete the synthetic operation, in seconds:
For synthetic full backup and GFS points: divide the expected size of the new full backup file (typically the same as previous full backup files) by the effective speed.
For all other synthetic operations, add the sizes of all of the incremental files which will be merged or transformed, and then divide the resulting sum by the effective speed. Typically only the oldest incremental file is merged, whereas all incremental files are transformed to rollbacks.
──────────────────────────────────────────────────────────
Slow restore or Surebackup
Worst case scenario where the backup file is heavily fragmented inside, which implies a lot of random read I/O:
C:\diskspd> diskspd.exe -b512K -r4K -h -d600 \\nas\share\VeeamBackups\Job\Job2014-01-23T012345.vbk
-r4K enables random I/O that are 4KB aligned, for a more realistic simulation.
Best case scenario where the backup file is not fragmented inside (no parallel processing), which implies linear read I/O:
C:\diskspd> diskspd.exe -b512K -h -d600 \\nas\share\VeeamBackups\Job\Job2014-01-23T012345.vbk
In both cases you need to pick an existing .vbk file as the target. Only read operations will be performed.
──────────────────────────────────────────────────────────
Direct disk access speed
C:\diskspd> diskspd.exe -h -d600 #X
Where X is the number of disk that you see in Disk Management.This will not overwrite any data, it is a safe test, and it works for Offline disks too. You can simulate and measure maximum possible reading speed in SAN or hot-add modes, however this of course will not take any VDDK overhead into account.
More Information
FAQQ: Can diskspd be used to stress-test NAS boxes for reliability ("specified network name is no longer available" errors in Veeam)
A: Unfortunately, no. If the SMB share disappears, diskspd will just ignore that issue. It is better to use Wireshark.
Q: Active full starts fast but then gradually becomes slower and slower. Target agent runs on Windows 2008 (not R2).
A: This is a known (yet undocumented) performance degradation issue on Windows 2008. Upgrade to or deploy 2008 R2 (or newer). In case of a CIFS repository you can force some other 2008 R2 server to be used as gateway/proxying. The issue itself can be demonstrated with diskspd if you set it to run for several hours, then observe how the write rate slowly goes down in Resource Monitor.
Q: I am getting extremely high I/O speed like 4 GB/s in any test I try, even though I have set the -h flag, what's going on?
A: Most likely you're running diskspd on a Hyper-V VM, testing performance of a virtualised (.vhdx) disk, so the data is cached by the Hyper-V host. Run the test on the datastore where that .vhdx is located instead.
↧
↧
Configuring a SQL staging server to a Veeam Explorer gives “error: 25”
Challenge
When configuring a staging SQL server for Veeam Explorers, the following error appears when a malformed server name is provided:A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 25 – Connection string is not valid)
Cause
The name for the staging server is malformed. Typically, this is the result of entering the SQL server as a UNC path.Solution
To correct this error, provide only the DNS name or IP address in the server name field.↧
How to move the Veeam Backup & Replication software to another server
Challenge
You need to move Veeam Backup & Replication software and database to a new server.Solution
Note: This section will refer to the server where Veeam Backup & Replication is installed prior to the move as the “old server”, and the location after the move as the “new server”.Performing migration using Configuration Backup:
Perform the following steps on the old server:
1. Stop and disable all jobs.
2. Perform configuration backup:
http://helpcenter.veeam.com/backup/80/vsphere/index.html?vbr_config_manually.html
3. Close Veeam GUI and stop all Veeam Services.
Perform the following steps on the new server:
1. Install Veeam Backup & Replication with a brand new DB.
2. Apply the latest patch to Veeam Backup & Replication: http://www.veeam.com/patches.html
3. Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
4. Perform configuration backup restore:
http://helpcenter.veeam.com/backup/80/vsphere/index.html?vbr_config_restore.html
Note: It will be necessary to re-enter the password for every account during restore of non-encrypted configuration backups.
5. Run a test job to make sure everything moved correctly.
Performing migration if Configuration Backup is not available:
Note: Use this option only if Configuration Backup is not available. If encryption was used on the previous installation, a newly installed backup server will not be able to decrypt such information if attached to the existing database, so any encrypted information will have to be supplied manually – existing encrypted backups have to be re-imported to provide the password.
Perform the following steps on the old server:
1. Stop and disable all jobs.
2. Close Veeam GUI and stop all Veeam Services.
3. Create backup of the SQL database. (http://www.veeam.com/kb1471)
To find out where the VeeamBackup database is located, open regedit on the old server and navigate to:
HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
There you will find 3 dword values:
- SqlServerName
- SqlInstanceName
- SqlDatabaseName
Perform the following steps on the new server:
1. Install Veeam Backup & Replication with a brand new DB.
2. Apply the latest patch to Veeam. http://www.veeam.com/patches.html
3. Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
4. Restore the Veeam database to the instance on the new server or on a SQL server which will host Veeam DB. (link)
5. Navigate to HKLM\SOFTWARE\Veeam\Veeam Backup and Replication and specify new values for the restored DB:
- SqlServerName
- SqlInstanceName
- SqlDatabaseName
6. Restart Veeam Services to apply the changes.
7. Open the Veeam console and using the “Manage Credentials” wizard from the main menu re-enter the password for every account.
8. Run a test job to make sure everything moved correctly.
More Information
Performing configuration backup on v.7: http://helpcenter.veeam.com/backup/70/vsphere/index.html?vbr_config_manually.htmlPerforming configuration restore on v.7: http://helpcenter.veeam.com/backup/70/vsphere/index.html?vbr_config_restore.html
Configuration backups created with version 7 are supported for restore on version 8.
In situations where physical local storage is used please see the following KB that details how to relocate Veeam Backup and Replication backup file locations: https://www.veeam.com/kb1729
↧
Exporting Veeam Endpoint backups as virtual hard disk files
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. Through 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:
- Create recovery media image (ISO) as described here.
- Create a backup of your system with Veeam Endpoint Backup.
- 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.
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.
↧
Release Notes for Veeam Backup & Replication 9.0 Update 1
Challenge
Release Notes for Veeam Backup & Replication 9.0 Update 1Cause
Please confirm you are running version 9.0.0.902 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console. If you are using partner preview build 9.0.0.773, you must upgrade to GA build 9.0.0.902 first by installing Day 0 Update > KB2084
After upgrading, your build will be version 9.0.0.1491
Prior to installing this update please reboot the Veeam server to clear any locks on the Veeam services and when the reboot is done, please stop all the Veeam jobs and services before applying the update.
After installing the update, during the first start of the Veeam Backup Service, required modifications will be made to the configuration database automatically to optimize its performance. These modifications may take up to 10 minutes to complete. Please do not reboot the Veeam server, or attempt to stop the service during this operation. If there is concern regarding the time that the Veeam Backup Service takes to start after upgrade, please contact Veeam Customer Support.
Once Veeam Backup Service starts, please open the console and allow Veeam Backup & Replication to update its remote components.
To obtain this update, please click here (you need to be logged in to download the update).
To obtain Veeam ONE v9 Update 1, please follow this link
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:General
- Enhanced extent selection logic for scale-out backup repositories with and without per-VM backup file chains enabled.
- Added reversed incremental backup mode support for storage-level corruption guard and backup file compact and defrag functionality.
- Guest Interaction Proxy selection algorithm has been improved to increase proxy selection performance.
- Added support for BitLooker folder exclusion functionality on Japanese and Chinese OS. This requires that the backup proxy used by the job is installed on the OS with the same locale as the processed VM.
Cloud Connect Replication
- Support for replica seeding.
- Support for replication from backup (except from backup files stored in cloud repositories).
- Improved failover issues reporting.
VMware
- Storage fingerprint check can now be disabled using SshFingerprintCheck (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key.
- Datastore based jobs can now be set to not include VMs with mounted ISO residing on the selected datastore. To enable this behavior, create StrictDatastoreScope (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key.
Hyper-V
- Replica disk exclusion and Linux file-level recovery should now work correctly on Windows Server 2012.
Application-aware processing
- To increase the chance of Microsoft VSS processing succeeding, the default VSS snapshot timeout has been doubled to 1200 sec. Additionally, VSSGuestSnapshotTimeout (DWORD) registry value in seconds under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key has been added to allow you to control this value.
Oracle
- Added support for Oracle ASM on GPT disks.
- Redo log backup for non-ASM deployments is now performed directly from logs directory, without first copying the logs into a temp folder.
- Added ability to skip NOARCHIVELOG mode databases without warnings. To enable this behavior, create OracleSkipNoArchiveLogDB (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the processed VM.
- Added ability to disable Oracle processing without having to disable application-aware processing for the rest of applications running on the same VM. To enables this behavior, create DisableOracleProcessing (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the processed VM.
- Improved reliability of abandoned log backup process termination in cases such as loss of network connectivity or backup repository reboot.
Veeam Explorers
- Improved Veeam Explorer for SQL Server startup and restore initialization time on large backup sets.
- Added support for exporting very large PST files with Veeam Explorer for Microsoft Exchange.
Tape
- Improved reliability of detecting, erasing, ejecting and exporting tapes.
- Improved GFS candidate restore point selection logic for certain scenarios.
SureBackup
- SureBackup jobs will no longer remove VM snapshot before deleting the temporary VM itself, thus speeding up job completion time. Instead, an additional functionality has been added to automatically clean up VM leftovers, which occasionally may be left on the datastore used for I/O redirection due to a VMware bug caused by deleting a VM with the existing snapshot.
- SureBackup role descriptions and application test scripts will now be obtained from the backup server, as opposed to the console.
User interface
- Improved user interface responsiveness and reduced configuration database SQL Server load in the environments with large amount of backups and replicas.
- Deduplicating storage appliance users will now receive a warning if their backup job or storage appliance settings do not match the recommended settings.
Enterprise Manager web UI
- Addressed cross site scripting web vulnerability has been discovered in Veeam Backup Enterprise Manager web interface. Veeam thanks Davide 'Peru' Peruzzi [GoSecure!] for vulnerability discovery.
Upgrade
- Console will now auto-update itself when connecting to backup server of higher version by downloading the update package (or updated files) directly from the backup server. This functionality is supported for both updates and hot fixes.
- Network extensions appliances are now included into the existing remote components auto update process (Upgrade wizard), thus removing the requirement to re-deploy them manually.
Veeam Cloud & Service Provider Partners
Starting from Update 1, when automatic license update is enabled, backup servers with per-VM hosting licenses will send protected VM counts for the past week (high watermark) to the Veeam licensing server. The collected data will allow our backend system to automatically approve monthly usage reports as long as they do not deviate significantly from any high watermark for the reporting period. It's the first of several steps Veeam is taking to streamline usage reporting and reduce processing costs. Automatic usage logging is currently optional and can be turned off by disabling automatic license update.
For the information on Veeam Cloud Connect infrastructure specific enhancements and bug fixes included in this update, please refer to the issue tracking topic in the private VCSP forum. If you are VCSP but don't have access, please apply to Cloud & Service Providers group using Veeam forum's User Control Panel.
More Information
To obtain this update, please click here (you need to be logged in to download the update).To obtain Veeam ONE v9 Update 1, please follow this link
↧
↧
Restoring domain controller from an application-aware backup
Challenge
Since Active Directory implements multi-master replication, where multiple domain controllers sync changes with each other, one of the key challenges is the DC recovery process. This article outlines different DC restore scenarios and goes into some specifics of when and why this or that type of restore is required as well as gives instructions on the manual steps to perform proper DC recovery from backup created with Veeam B&R.Before going into details, it is worth stressing that by default Veeam B&R performs automated non-authoritative restore of domain controller and in most cases when you need to recover failed DC, authoritative restore is not required.
The following situations are possible:
- Restoring single lost DC in a multi-DC environment
- Restoring entire AD infrastructure (AKA “all DC’s are lost”)
- Restoring from Active Directory corruption
Depending on the scenario, different steps (or no steps at all) are required to perform DC restore. All of the scenarios assume application-aware image processing was enabled in the backup job that backed up the DC being restored.
Solution
Restoring single lost DC in a multi-DC environmentThis scenario, actually the most common one, incurs restoring just one of the multiple DC’s when there are still other functional DC’s in the environment that the restored DC can replicate changes from.
DC recovery with Veeam B&R in this case is fully automated and does not require any user interaction. If your backup was done with application-aware image processing enabled in the backup job settings, Veeam B&R performs a non-authoritative restore of the DC, where the restored VM should first boot in Directory Services Restore Mode (DSRM) mode and then reboot automatically immediately to boot up next time normally.
The domain controller itself will understand that it has been recovered from backup and will allow normal replication to update everything that has been changed since the backup took place.
The automatic recovery should also work for environments with only a single DC.
Restoring entire AD infrastructure (AKA “all DC’s are lost”)
As mentioned above, the automatic recovery process performs a non-authoritative restore, where the DC reboots and starts looking for other DC’s to sync up. However, in a scenario where all DC’s are gone, there are no other partners available and replication may take quite long (15-30 minutes) to start. To avoid wasting the time attempting to contact replication partners, it is recommended to restore two of the domain controllers at once, power them on, wait for their reboot and force one of them to become authoritative for SYSVOL, so that they can start replicating. Then restoring other DC’s will be similar to the first scenario, i.e. will be 100% automatic.
Note: During the restore procedure, make sure the restored DC’s DNS records point to available DNS servers (e.g. to itself).
The procedure for designating DC as authoritative for SYSVOL varies based on whether FRS or DFS-R is used for SYSVOL replication. Here we discuss the steps for DFS-R as the more widely used these days (recovery with FRS might need additional manual steps), which are basically consist of setting the following registry values:
Key: HKLM\System\CurrentControlSet\Services\DFSR\Restore
Value: SYSVOL (REG_SZ) = “authoritative”
Key: HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\SystemStateRestore
Value: LastRestoreId (REG_SZ) = any GUID value (e.g. 10000000-0000-0000-0000-000000000000)
If the first restored DC already hosts operations master roles, set the following registry value in order to bypass initial synchronization requirements and not to wait for another partners to replicate the directory partitions:
Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Value: Repl Perform Initial Synchronizations (REG_DWORD) = 0
Note: Don’t forget to reset this value back to 1 after domain recovery is completed, so that domain controller has successful replication with its partners before starting to service client requests.
After setting the values above, restart the domain controller.
Notes:
• If you’re restoring DC without FSMO roles, you might want to transfer them to it manually after the restore, using the ntdsutil seize command.
• This type of restore is similar to what Veeam B&R performs automatically when restoring DC within SureBackup isolated virtual lab.
Restoring from Active Directory corruption
Scenario where no DC’s are actually lost, however, AD itself is damaged in some way (corrupt objects or schema) and you need to restore from the backup created before corruption occurred. In this case you need to restore one of the multiple DC’s when other DC’s are still operating a damaged copy of AD and force all of them to accept replication changes from the restored DC. This is where authoritative restore of the DC is required.
Note: It is recommended to perform restore with network disabled to prevent DC from accepting changes from other controllers after the default non-authoritative restore.
To perform an authoritative restore:
1. Restore the DC and let it complete the default non-authoritative restore (wait until it reboots second time).
2. During this second boot, press F8 to get to DSRM mode.
3. Log in with DSRM account and password.
4. Open a command prompt and run ntdsutil command.
5. At the "ntdsutil:" prompt, type "authoritative restore" and press Enter.
6. At the "ntdsutil authoritative restore:" prompt, type "restore database" and press Enter.
7. At the Authoritative Restore Confirmation dialog box, click Yes.
8. Upon restore completion, type "quit" and press Enter to exit the ntdsutil utility.
9. Reboot server.
10. Perform an authoritative restore of the SYSVOL, as was already discussed above.
Note: For an easier item-level recovery of Active Directory objects (without the need to restore the domain controller itself), consider using Veeam Explorer for Active Directory.
More Information
Veeam recovery of a domain controllerActive Directory backup and recovery with Veeam
Recovering Your Active Directory Forest
Windows Server - How to Perform an Authoritative Restore of Active Directory Object
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 1)
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 2)
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 3)
↧
How to Change the settings related to Veeam Backup & Replication Log Files
Challenge
This article documents how to change the defaults for the following settings:1. The absolute log file directory from which all logs will be stored.
2. Maximum size each log is allowed to reach before beginning a new log file.
3. Number of archived logs to be kept before removal.
4. The total size for a job’s logs to reach before Veeam will begin archiving (gzip) inactive logs to save space.
5. Amount of logs that are archived per job.
Note: After making changes to these setting the Veeam server must be restarted to apply changes and ensure that previous log files are unlocked.
Solution
The following registry keys are used to manage log file location, file size and count:Note: All registry values are to be set within the key HKLM\SOFTWARE\Veeam\Veeam Backup and Replication on the server where the Veeam Backup & Replication console is installed.
* These values may need to be created if they are not present in the registry. If the settings you currently have are default, then you will need to add these values as they will not inherently already exist.
──────────────────────────────────────────────────────────
*1. Default log directory location:
Type: String
Name: LogDirectory
Data: <Path>
Example:
──────────────────────────────────────────────────────────
2. Maximum file size. New files are created when a file reaches the set max size.
Example: Svc.VeeamBackup.log -> Svc.VeeamBackup_1.log
Type: DWORD
Name: MaxLogSize
Data: <value in KiB>
Default: 10240 (binary)
──────────────────────────────────────────────────────────
3. Maximum log count. Number of log generations to retain.
Example: Svc.VeeamBackup_1.log, Svc.VeeamBackup_2.log, etc.
Type: DWORD
Name: MaxLogCount
Data: <numeric value>
Default: 10
──────────────────────────────────────────────────────────
*4. Total size of uncompressed logs, applies per job.
Type: DWORD
Name: UncompressedLogsMaxTotalSize
Data: <value in KiB>
Default: 512000
──────────────────────────────────────────────────────────
*5. Total amount of archived generations of logs
Example: Svc.VeeamBackup.1.gz Svc.VeeamBackup.2.gz
Type: DWORD
Name: LogsArchivesMaxCount
Data: <numeric value>
Default: 10
──────────────────────────────────────────────────────────
↧
Application is Shutting Down
Challenge
Jobs of any type fail with the error, “Application is shutting down.” For example:Application is shutting down. Failed to download disk. Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}
BackupSynthesizedStorageToTape failed Application is shutting down. Unable to receive file. Application is shutting down.
In Event Viewer on the Veeam Backup & Replication server, a time change of several minutes is recorded in the System log a few minutes before the error occurs:
SEVERITY:Informational
SOURCE:Microsoft-Windows-Kernel-General
EVENT ID:1
DESCRIPTION:System time changed from 2016-03-31T12:06:22.375327200Z to 2016-03-31T12:12:23.623952000Z.
Cause
The Veeam Backup Service uses a system of timed leases as part of monitoring the many processes it manages. Usually this error involves a five minute lease for the VeeamAgent processes (Data Movers). When the Veeam Backup Service is operating normally, this lease is continually renewed. If the lease expires, the associated process is shut down.Typically the lease will expire either because the system time has changed by several minutes, or because a problem communicating with the Veeam Backup Configuration Database has prevented the Veeam Backup Service from renewing the lease.
Solution
On VMware virtual machines, VMware Tools will periodically synchronize the system time with the ESXi host. If the time on the host differs from the NTP server used by Windows, the system time will repeatedly shift between the two different times. The best solution is to synchronize the time on the ESXi host, the Veeam Backup & Replication server and/or the domain controllers to the same source. If this is not possible, you should disable VMware Tools time synchronization for the Veeam Backup & Replication server.As a quick but incomplete workaround, you can run the following from the command line on the Veeam Backup & Replication server:
"c:\Program Files\VMware\VMware Tools\VMwareToolboxcmd.exe" timesync disable
If time synchronization does not appear to be the problem, please contact Veeam Support.
More Information
VMware KB: Timekeeping best practices for Windows, including NTP↧