Veeam One - Steps to Compile Logs

September 26, 2017, 7:21 am

≫ Next: How to use DiskSpd to simulate Veeam Backup & Replication disk actions

≪ Previous: Moving Veeam ONE database to a different SQL Server

$

0

0

Challenge

In some cases, logs will need to be reviewed by Veeam Support to help diagnose issues.

Solution

There are 2 ways to compile logs: 

1. Monitor Server and Monitor Client logs (If Remote Monitor client is being used these logs may be requested in addition to server logs): 

Open Veeam ONE Monitor and navigate to Help -> Support Information 

Once complete click Open folder to open location of extracted logs then upload to Customer portal or FTP as explain below.

 

2. All Veeam One logs for all components (Monitor, Reporter, Business View, etc.): 

In Veeam One Monitor console navigate to Options > Server Settings > Other Settings > Launch Support Utility. In the lower left corner click Export Logs 
or 
Browse to or run "C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe"

Exporting logs may take a while. When it is finished, you will be asked to choose the location for the logs to be saved to.
 

 

Please attach these to your case, or in the event that the total attachment size is under 3.5MB, you may attach via email reply.

 
If none of these options for upload are working, please notify Veeam Support and an engineer will provide FTP credentials for the case. Once you receive the FTP link, follow the below instructions to upload the logs via FTP. You can start by copy and pasting the URL with credentials, as this has the credentials built into the link. Once you have copied the URL, you can use a Windows\File Explorer browser (windows key + e) and paste the link into that browser, or your preferred FTP client.

Note: Internet Explorer, Firefox, or any other browser will not work for the FTP upload.

1. Open Windows\File Explorer.
 
 
 2. Paste URL with credentials.
 
 
 3. Drag and Drop the Zipped folder or individual logs into the browser.

 
 4. Once completed, e-mail your Veeam Support engineer to inform them the logs have been successfully uploaded to ensure the quickest review and response.
 

More Information

Below are the relative log path lists for Veeam One. If there are difficulties compiling the logging requested via the Veeam One support tool instructions above, please obtain the files from the appropriate directory below and provide Veeam Support a .zip file copy.

For versions: 7.x, 8.x, 9.x:
Veeam ONE Monitor - C:\Users\<USER>\AppData\Local\Veeam\Veeam ONE Monitor\
Veeam Reporter\Business View Service logs - C:\Users\<USER>\AppData\Local\Veeam\Veeam ONE\
Veeam Reporter Web logs - %ProgramFiles%\Veeam\Veeam ONE\Veeam ONE Reporter Web\Veeam\Veeam ONE Reporter\
Veeam Business View Web logs - %ProgramFiles%\Veeam\Veeam ONE\Veeam ONE Business View Web\Generated\
VeeamOneSettings - C:\Users\<USER>\AppData\Local\Veeam\VeeamOneSettings\

Starting from version 9.5:
Veeam ONE Monitor – %ProgramData%\Veeam\Veeam ONE Monitor\Logs\
Veeam Reporter\Business View Service logs – %ProgramData%\Veeam\Veeam ONE\
Veeam Reporter Web logs – %ProgramFiles%\Veeam\Veeam ONE\Veeam ONE Reporter Web\Veeam\Veeam ONE Reporter\
Veeam Business View Web logs – %ProgramFiles% \Veeam\Veeam ONE\Veeam ONE Business View Web\Generated\
VeeamOneSettings - %ProgramData%\Veeam\VeeamOneSettings\

If you have any questions, contact Veeam Support.

---

How to use DiskSpd to simulate Veeam Backup & Replication disk actions

September 26, 2017, 7:22 am

≫ Next: Mapping an existing Veeam Agent for Microsoft Windows backup chain to a Veeam Backup & Replication repository

≪ Previous: Veeam One - Steps to Compile Logs

$

0

0

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 and additional info 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+ (4MB; 8MB for v8 and earlier), 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
-Sh 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\x86fre> diskspd.exe -c1G -b512K -w100 -Sh -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

C:\diskspd\x86fre> diskspd.exe -c1G -b512K -w67 -r4K -Sh -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\x86fre> diskspd.exe -c1G -b512K -w50 -r4K -Sh -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

This is typically when you're restoring from deduplication appliances with sub-optimal settings. See [1] and [2] for the recommended settings. As a workaround in case of slow restore, manually copy the backup files elsewhere (e.g. Veeam server), import and restore from there.

Worst case scenario where the backup file is heavily fragmented inside, which implies a lot of random read I/O:

C:\diskspd\x86fre> diskspd.exe -b512K -r4K -Sh -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\x86fre> diskspd.exe -b512K -Sh -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\x86fre> diskspd.exe -Sh -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

FAQ
Q: 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 -Sh 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.

Mapping an existing Veeam Agent for Microsoft Windows backup chain to a Veeam Backup & Replication repository

September 28, 2017, 5:42 am

≫ Next: Cannot restore to the backup repository host when storage VSP is enabled

≪ Previous: How to use DiskSpd to simulate Veeam Backup & Replication disk actions

$

0

0

Challenge

You need to map an existing Veeam Agent for Microsoft Windows backup chain to a Veeam Backup & Replication repository

Cause

There are no features in Veeam Agent for Microsoft Windows that would allow mapping existing backups to Veeam Backup & Replication, however it is possible to copy a local backup chain to a Veeam Backup & Replication repository and continue using it.

Solution

Here is the list of steps for mapping a local backup chain to a Veeam Backup & Replication repository.

1. Create a backup with Veeam Agent for Microsoft Windows at any temporary backup destination of your choice.

If a Veeam Backup & Replication repository was used,

• remove the existing Veeam Agent for Microsoft Windows backup job from jobs (right lick > Delete)
• remove the backup files from configuration: right click Disk (backups) > Endpoint Backups > Remove from configuration. 

2. Place the backup chain into the required folder.

2.1 Example for a non-cloud repository

Backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a Veeam Backup & Replication repository into the following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the account that is used to access the repository. In this example, the account is DOMAIN1\user1, so the folder name would be DOMAIN1_user1.

The complete path to the backup files would be C:\Backup\DOMAIN1_user1\Backup Job 1

2.2 Example for a cloud repository

The backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a cloud Veeam repository into following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the tenant account that is used to access the repository. If the account name is Tenant2, the complete path to the backup files would be C:\Backup\Tenant2\Backup Job 1

If a subtenant is used with the account name Subtenant3, the path will be C:\Backup\Tenant2\users\Subtenant3\Backup Job 1

3. Rescan the Veeam Backup & Replication repository. Here is a brief guide on repository rescan.

4. The Veeam Agent for Microsoft Windows backup should appear under Disk > Imported.

5. Point the Veeam Agent for Microsoft Windows job to the required Veeam Backup & Replication repository. Do not run it immediately, just close the wizard after making the changes.

6. On the Veeam Backup & Replication machine, the backup should be moved from the Imported section to Backup > Disk. Make sure that backups are located in Backups > Disks (not Disk (imported)).

7. Run the Veeam Agent for Microsoft Windows backup job. It should continue the imported backup chain.

Note: The described solution works for Veeam Backup & Replication repository and Veeam Cloud Connect repository.

More Information

If you have any questions, open a case with Veeam Support.

Cannot restore to the backup repository host when storage VSP is enabled

September 29, 2017, 2:23 am

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

≪ Previous: Mapping an existing Veeam Agent for Microsoft Windows backup chain to a Veeam Backup & Replication repository

$

0

0

Challenge

Hyper-V Instant Recovery or SureBackup fail with the error message, “Cannot restore to the backup repository host when storage VSP is enabled.”

Cause

In previous versions of Veeam Backup & Replication, Instant Recovery or SureBackup with a specific repository configuration could in some circumstances cause I/O freeze of a volume or hang of the VSS framework on a Hyper-V host. In Veeam Backup & Replication v8, this configuration has been disallowed.
 
The configuration is:

• The repository data mover process is running in a Hyper-V virtual machine.
• The host running that virtual machine is also running the SureBackup virtual lab or is the target host for Instant Recovery.
• The host has storage I/O balancing enabled (this is a default setting in Server 2012 and later).

Solution

There are several solutions available, depending on your circumstances:
 
If another Hyper-V host is available:
Restore to a different Hyper-V host, or create the SureBackup virtual lab on a different Hyper-V host.
 
If the repository is a CIFS/SMB share or Data Domain Boost repository:
The repository data mover must run on a Windows OS. By default, this “gateway server” will be selected automatically from among all managed Windows servers added to the backup infrastructure without regard for the limitation described in this KB. You can specify a different gateway server in the repository settings.
User Guide: How to specify shared folder repository settings
 
If you have other storage available:
Copy the backup files to this other storage, then add it to the Backup and Replication console as a repository. When you have verified that you are able to restore from the backup files in this new location, you can delete the old files and map the backup jobs to the new files:
KB1729: How to Move Veeam Backup & Replication Backup Files
 
In the event of an emergency restore when no other options are available:
Perform full VM restore instead of Instant Recovery.
User Guide: How to perform full VM restore

More Information

Performance Tuning Guidelines for Windows Server 2012 describes I/O balancing:
“The virtualization stack balances storage I/O streams from different virtual machines so that each virtual machine has similar I/O response times when the system’s I/O bandwidth is saturated.” The document goes on to describe options for tuning or disabling this setting, but notes: “We do not recommend this advanced tuning option unless you have a specific reason to use it. These registry keys may be removed in future releases.”
 

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

October 2, 2017, 12:52 pm

≫ Next: Error: Couldn’t Create Crypto Provider (Monitor Fails to Launch)

≪ Previous: Cannot restore to the backup repository host when storage VSP is enabled

$

0

0

Challenge

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

Cause

Conflict with BusinessView component installation directory

Solution

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

Error: Couldn’t Create Crypto Provider (Monitor Fails to Launch)

October 2, 2017, 1:13 pm

≫ Next: Veeam VMware Collector: VMware connection is unavailable

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

$

0

0

Challenge

VeeamONE Monitor Fails to Launch with Error Message: Couldn’t Create Crypto Provider

Cause

Known Microsoft issue per KB 3000850: https://support.microsoft.com/en-us/kb/3000850

Solution

Adjust registry to show previously deleted nodes/child objects and resolve the alarms.
    1. On the Veeam ONE Server: Click Start, click Run, type regedit, and then click OK.
    2. Navigate to the following path:   HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb3.
    3. Next, right-click on the folder (in the left-hand pane of the Registry Editor) and select New | DWORD. The name of the new registry entry will be selected for editing. Type "ProtectionPolicy" and then press ENTER.
    4. Right-click on the new ProtectionPolicy registry entry and then click Modify.
    5. In Edit DWORD Value, change the Value to 1
    6. Once finished, click OK. Then, restart the computer.
    7. Relaunch the Monitor Client.

More Information

Alternatively, user can attempt to Shift + Right Click the Monitor Icon and Run as a Different User. This will sometimes allow access as well, but is not a permanent solution.
 

Veeam VMware Collector: VMware connection is unavailable

October 2, 2017, 1:14 pm

≫ Next: VeeamONE Installation Fails during SQL Installation

≪ Previous: Error: Couldn’t Create Crypto Provider (Monitor Fails to Launch)

$

0

0

Challenge

Troubleshooting Steps for when you get “Veeam VMware Collector: VMware connection is unavailable” 

 

Cause

A few issues can cause that are mostly resource related.

Solution

First we will want to verify the connection the Collectors have to the vCenter.
      - First go onto the Collector server and verify the service ‘Veeam VMware Collector’ is running
      - After that verify the credentials are correct. You can do that by following this link in the user’s guide https://helpcenter.veeam.com/mp/80/vmware_guide/index.html?basic_configuration_launch_web_ui.html
      - After this has been verified it may be a good time to analyze if you need to add more collectors. If this error started happening after you added a host or some VM’s then it may be required. Using the install media for Management pack you can run a collector only installation on a server to see If this resolves the issue or you can deploy the collector through SCOM as well.
 
This link below will help you with the collector only installation.
       - https://helpcenter.veeam.com/mp/80/vmware_guide/index.html?collector_only_installation.html
 
Usually these steps will resolve the issue. The most common solution is having to add additional collectors. If these steps did not work, then please create a ticket with support.
 

More Information

https://helpcenter.veeam.com/mp/80/vmware_guide/index.html?collector_only_installation.html
 
https://helpcenter.veeam.com/mp/80/vmware_guide/index.html?basic_configuration_launch_web_ui.html
 

VeeamONE Installation Fails during SQL Installation

October 2, 2017, 1:15 pm

≫ Next: Enterprise Plus license is required error on dashboards and reports

≪ Previous: Veeam VMware Collector: VMware connection is unavailable

$

0

0

Challenge

When trying to perform a new installation, VeeamONE gets to the initial Creation of the SQL instance and fail with general error; installation log shows error: No Such Service Found

Installation Log will have the error:
     [Date/Time][ERROR] System.Exception: No such service found.
     at Veeam.Setup.Common.Util.ServiceManager.InitController()
     at Veeam.Setup.Common.Util.ServiceManager.Create(String serviceName, String processName)
     [Date/Time][INFO] Service is not installed, skipping.
     [Date/Time][INFO] Service name: VeeamRSS
     [Date/Time][INFO] Service obsolete name: Not specified
     [Date/Time][INFO] Service process: Not specified
 

Cause

VeeamONE requires full access to use TLS 1.0

Solution

Enable TLS 1.0 In Internet options. Also make sure to allow or enable TLS 1.0 Access in any security/crypto/firewall software being used.
 
To Enable TLS 1.0 in Internet Options:

1. Open Control Panel and locate Internet Options (or access via Internet Explorer)
2. Go to the Advanced tab
3. Scroll down to locate ‘Use TLS 1.0’ under Security
4. Check the box to enable. Then hit Apply and Ok.
5. Close and Internet Browser Currently open
6. Restart Installer

More Information

Note:

• If install still fails to same problem, the environment likely has security/crypto software in place that is blocking TLS 1.0 use.
• TLS 1.0 is an older software communication encryption protocol that allows our software to still be ran on older server versions.

---

Enterprise Plus license is required error on dashboards and reports

October 2, 2017, 1:18 pm

≫ Next: Repository does not exist

≪ Previous: VeeamONE Installation Fails during SQL Installation

$

0

0

Challenge

Verify health of Data Warehouse  

Cause

Veeam MP license is synchronized to the Data Warehouse then the 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

Repository does not exist

October 5, 2017, 5:24 am

≫ Next: Upgrade failed: Repository does not exist

≪ Previous: Enterprise Plus license is required error on dashboards and reports

$

0

0

Challenge

When trying to delete a repository, you receive a "the Repository does not exist: <GUID>" error.

Cause

The problem occurs when trying to delete a repository after upgrading from VBO 1.0 to 1.5, if the service was running under a domain account and the repository was located on an SMB share. After upgrading to v1.5, the services run under the local system account.

Solution

Give the account running the services on your VBO server access rights to the repository, and then delete it.

Upgrade failed: Repository does not exist

October 5, 2017, 5:28 am

≫ Next: Veeam Backup & Replication Console Fails to Open After a Hostname Change

≪ Previous: Repository does not exist

$

0

0

Challenge

After upgrading VBO to version1.5, out of date repository upgrade fails with an “Upgrade failed: Repository does not exist” error.

The following can be found in the proxy log files:
[Timestamp]   99 (6232) Error: Access is denied
[Timestamp]   99 (6232) Stack:
[Timestamp]   99 (6232)    at Veeam.Engine.FreeSpaceController.FreeSpaceInfo.GetFreeSpaceInfo(String uncPath)
   at Veeam.Archiver.Proxy.ProxyFileSystemProvider.GetFreeSpaceInfo(String path)
   at Veeam.Archiver.Proxy.Proxy.ProxyFileSystemService.GetDiskInfo(String path)
   at Veeam.Archiver.Proxy.Proxy.ProxyAdmin2.GetDiskInfo(String path)
   at SyncInvokeGetDiskInfo(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Cause

This issue occurs if the services were running under a domain account prior to the upgrade and the repository was located on an SMB share. After upgrading to v1.5, access to this share may be lost, because services in the new version run under the local system account.

Solution

Give the account running the services on your VBO server access rights to the repository

More Information

If the repository was accessed via an administrative share (e.g. c$), you need to change this to a direct path to the repository.

Veeam Backup & Replication Console Fails to Open After a Hostname Change

October 5, 2017, 6:02 am

≫ Next: LVMDriver : Failed to create LVM Instance

≪ Previous: Upgrade failed: Repository does not exist

$

0

0

Challenge

If the hostname is changed for a machine with Veeam Backup & Replication installed the console may fail to open with an error, shown in the following screenshot:

The Veeam Backup service will be stopped. Attempting to start the Veeam Backup service results in the issue shown by the following screenshot:

Logging will show the Veeam Backup service attempting to connect to SQL using the previous hostname. %programdata%\Veeam\Backup\Svc.VeeamBackup.log:

Info [DB] Connecting to SQL Server (CurrentUser=[NT AUTHORITY\SYSTEM], ServerInstance=[<OldHostname>\<SQLInstanceName>], Options=[Direct])
Info [DB|ERROR] Failed to connect to server. 

Cause

The Veeam product is configured to use the machine’s previous hostname to connect to the Veeam Backup SQL database. 

Solution

To fix this issue, update the product configuration with the current hostname by following these steps:

• Open the Configuration Database Connection Settings program, which should appear in the all programs menu of the Veeam Backup & Replication server.
• Within this program, select Veeam Backup and Replication then click next.
• Look for Server name. This field is formatted as such: <Hostname>\<SQLInstanceName>

• Change the first portion of Server name to match the Veeam Backup & Replication machine’s current hostname and click next.
• Veeam will connect to the database. Wait for this process to complete, click Next and the Veeam service will be started. When this has completed click Finish, then try accessing the Veeam Backup & Replication console.

More Information

Troubleshooting for issues opening the console when the hostname has NOT changed are available here: https://www.veeam.com/kb2127
 
Hostname changes of other devices such as VM hosts, repository or proxy servers will require additional steps not covered by this KB.
 
If there are any problems following these steps, please contact Veeam Support. The Veeam service failing to start qualifies as a Severity 1 issue provided you do not have any other Veeam consoles and meet the criteria for a severity 1 issue as defined here: https://www.veeam.com/veeam_software_support_policy_pg.pdf

LVMDriver : Failed to create LVM Instance

September 8, 2017, 8:48 am

≫ Next: How to Re-create the Database of Veeam Agent for Microsoft Windows

≪ Previous: Veeam Backup & Replication Console Fails to Open After a Hostname Change

$

0

0

Challenge

In RHEL 7.4, Veeam Agent for Linux operations such as job runs or job creation are failing with the following error:

LVMDriver : Failed to create LVM Instance

Cause

With RHEL 7.4, the default global unit setting in the /etc/lvm/lvm.conf changed from 

units = "h"

to

units = "r"

This value option is not recognized by some distributions and programs. It interferes with the operations of Veeam Agent for Linux.

Solution

Before implementing this change, please check with your Linux Administrator that they approve of updating the global unit setting from “r” to another value. You can find a full list of available unit options at this RHEL link.

More Information

If the lvm.conf file doesn’t show a units value of “r”, please open a support case for further investigation. 

How to Re-create the Database of Veeam Agent for Microsoft Windows

September 15, 2017, 6:56 am

≫ Next: Veeam Backup & Replication - SQL Backup Guide: Using Microsoft SQL Server Agent With Application - Aware Image Processing

≪ Previous: LVMDriver : Failed to create LVM Instance

$

0

0

Challenge

Veeam Support is instructing you to re-create the database of Veeam Agent for Microsoft Windows.

Cause

The Veeam Agent for Microsoft Windows database files have been corrupted.

Solution

Perform the following actions:

1. Run regedit.exe and locate the HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup key. Create the following value under this key:
Name = Recreatedatabase 
Type = DWORD 
Value = 1 

2. Go to Control panel > Administrative Tools and run Services. Restart the Veeam Agent for Microsoft Windows service.

A new database instance will be created (this usually happens within 5 minutes).

Veeam Backup & Replication - SQL Backup Guide: Using Microsoft SQL Server Agent With Application - Aware Image Processing

September 19, 2017, 7:05 am

≫ Next: Repository does not exist

≪ Previous: How to Re-create the Database of Veeam Agent for Microsoft Windows

$

0

0

Challenge

This guide was created to assist you with successfully backing up, and restoring, Microsoft SQL databases.

Cause

Some highlights from this guide:

• Veeam Backup v7 most commonly used restore options for SQL
• Veeam Backup Job Configuration when backing up SQL
• Log Truncation, when and when not to use it
• Excluding the .bak and .trn Files
• Many more technical considerations included

Solution

Direct link for Veeam Backup & Replication 9.0:
Veeam Backup & Replication SQL Backup Guide

Direct link for Veeam Backup & Replication 9.5:
Veeam Backup & Replication SQL Backup Guide
 

---

Repository does not exist

October 5, 2017, 5:24 am

≫ Next: Upgrade failed: Repository does not exist

≪ Previous: Veeam Backup & Replication - SQL Backup Guide: Using Microsoft SQL Server Agent With Application - Aware Image Processing

$

0

0

Challenge

When trying to delete a repository, you receive a "the Repository does not exist: <GUID>" error.

Cause

The problem occurs when trying to delete a repository after upgrading from VBO 1.0 to 1.5, if the service was running under a domain account and the repository was located on an SMB share. After upgrading to v1.5, the services run under the local system account.

Solution

Give the account running the services on your VBO server access rights to the repository, and then delete it.

Upgrade failed: Repository does not exist

October 5, 2017, 5:28 am

≫ Next: Veeam Backup & Replication Console Fails to Open After a Hostname Change

≪ Previous: Repository does not exist

$

0

0

Challenge

After upgrading VBO to version1.5, out of date repository upgrade fails with an “Upgrade failed: Repository does not exist” error.

The following can be found in the proxy log files:
[Timestamp]   99 (6232) Error: Access is denied
[Timestamp]   99 (6232) Stack:
[Timestamp]   99 (6232)    at Veeam.Engine.FreeSpaceController.FreeSpaceInfo.GetFreeSpaceInfo(String uncPath)
   at Veeam.Archiver.Proxy.ProxyFileSystemProvider.GetFreeSpaceInfo(String path)
   at Veeam.Archiver.Proxy.Proxy.ProxyFileSystemService.GetDiskInfo(String path)
   at Veeam.Archiver.Proxy.Proxy.ProxyAdmin2.GetDiskInfo(String path)
   at SyncInvokeGetDiskInfo(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Cause

This issue occurs if the services were running under a domain account prior to the upgrade and the repository was located on an SMB share. After upgrading to v1.5, access to this share may be lost, because services in the new version run under the local system account.

Solution

Give the account running the services on your VBO server access rights to the repository

More Information

If the repository was accessed via an administrative share (e.g. c$), you need to change this to a direct path to the repository.

Veeam Backup & Replication Console Fails to Open After a Hostname Change

October 5, 2017, 6:02 am

≫ Next: HCL - Dell EMC Isilon

≪ Previous: Upgrade failed: Repository does not exist

$

0

0

Challenge

If the hostname is changed for a machine with Veeam Backup & Replication installed the console may fail to open with an error, shown in the following screenshot:

The Veeam Backup service will be stopped. Attempting to start the Veeam Backup service results in the issue shown by the following screenshot:

Logging will show the Veeam Backup service attempting to connect to SQL using the previous hostname. %programdata%\Veeam\Backup\Svc.VeeamBackup.log:

Info [DB] Connecting to SQL Server (CurrentUser=[NT AUTHORITY\SYSTEM], ServerInstance=[<OldHostname>\<SQLInstanceName>], Options=[Direct])
Info [DB|ERROR] Failed to connect to server. 

Cause

The Veeam product is configured to use the machine’s previous hostname to connect to the Veeam Backup SQL database. 

Solution

To fix this issue, update the product configuration with the current hostname by following these steps:

• Open the Configuration Database Connection Settings program, which should appear in the all programs menu of the Veeam Backup & Replication server.
• Within this program, select Veeam Backup and Replication then click next.
• Look for Server name. This field is formatted as such: <Hostname>\<SQLInstanceName>

• Change the first portion of Server name to match the Veeam Backup & Replication machine’s current hostname and click next.
• Veeam will connect to the database. Wait for this process to complete, click Next and the Veeam service will be started. When this has completed click Finish, then try accessing the Veeam Backup & Replication console.

More Information

Troubleshooting for issues opening the console when the hostname has NOT changed are available here: https://www.veeam.com/kb2127
 
Hostname changes of other devices such as VM hosts, repository or proxy servers will require additional steps not covered by this KB.
 
If there are any problems following these steps, please contact Veeam Support. The Veeam service failing to start qualifies as a Severity 1 issue provided you do not have any other Veeam consoles and meet the criteria for a severity 1 issue as defined here: https://www.veeam.com/veeam_software_support_policy_pg.pdf

HCL - Dell EMC Isilon

October 5, 2017, 10:30 am

≫ Next: Veeam Agent for Linux Becomes Unresponsive on Debian

≪ Previous: Veeam Backup & Replication Console Fails to Open After a Hostname Change

$

0

0

Challenge

Product Information: 

Product Family: Dell EMC Isilon 
Status: Veeam Ready Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features. 

Solution

Product Details: 

Model number: All 
Number of Drives: Any 
Drive type: Any 
Firmware version: OneFS 8.0 
Additional support: Any EMC Isilon configuration with supported firmware. 
General product family overview: THE ISILON ADVANTAGE  
Dell EMC Isilon scale-out NAS is the ideal platform to store, manage and protect unstructured data efficiently while supporting a wide range of applications and workloads.  

Key advantages of Isilon scale-out NAS include:  
• Simple to manage: Single file system, single volume, global namespace  
• Massively scalable: Start small and scale to 10s of petabytes in a single cluster  
• Extreme performance: Support your most demanding file workloads with Isilon solutions that deliver up to 9 million IOPS and up to 540 GB/s aggregate throughput on a single cluster  
• Highly efficient: Over 80% storage utilization with data deduplication options to further reduce storage requirements by up to 30%  
• Ultra-dense hardware design: Provides 4 Isilon nodes in a single 4U chassis and reduces data center space requirements and related costs by up to 75%  
• Storage tiering: Optimize resources with policy-based, automated storage tiering to move data automatically to lower cost tiers, including cloud storage with a choice of cloud storage providers  
• Operational flexibility: Support a wide range of file workloads on a single platform with built-in multi-protocol capabilities including NFS, SMB, HTTP, FTP, and HDFS  
• Enterprise data protection: Isilon storage platforms are highly resilient, with up to N+4 redundancy, and offer proven enterprise-grade back-up and disaster recovery options  
• Robust security options: RBAC, Access Zones, SEC 17a-4 WORM compliance, File System Auditing, Data At Rest Encryption with SEDs, STIG hardening, CAC/PIV Smartcard authentication, and FIPS 140-2 validation  

 

Veeam Details: 

Veeam Build Number: 9.5.0.823 
Veeam Settings:  

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

More Information

Company Information: 

Company name: Dell EMC 
Company overview: Dell EMC, a part of Dell Technologies, enables organizations to modernize, automate and transform their data center using industry-leading converged infrastructure, servers, storage and data protection technologies. This provides a trusted foundation for businesses to transform IT, through the creation of a hybrid cloud, and transform their business through the creation of cloud-native applications and big data solutions. Dell EMC services customers across 180 countries – including 98 percent of the Fortune 500 – with the industry’s most comprehensive and innovative portfolio from edge to core to cloud. 

Veeam Agent for Linux Becomes Unresponsive on Debian

October 9, 2017, 8:29 am

≫ Next: How to Backup Your Veeam ONE SQL database

≪ Previous: HCL - Dell EMC Isilon

$

0

0

Challenge

When starting any backup job or log export, Veeam Agent  for Linux UI freezes and becomes unresponsive. The /var/log/veeam/Backup folder contains no log files for your configured backup jobs, the related folders are empty.  It may also be observed that veeamservice takes too much time to start/stop and becomes unresponsive.

Cause

It is possible that some of the dependent libraries are missing. The /usr/sbin/veeamjobman binary may not work properly if any dependent library missing. The example below contains the command that can be used to verify the root cause and the output generated in case a dependent library is missing.
 

root@debian:~# veeamjobman
veeamjobman: error while loading shared libraries: libmagic.so.1: cannot open shared object file: No such file or directory
root@debian:~#

The described behavior has been reproduced on Debian 7 and 8. For the most part, the minimal installations are affected.

Solution

The following workarounds are available at the moment.

• Try to install a package that contains the missing library.
• Upgrade the current system to the most recent update.

A package that contains the missing library can be found like this:
 

root@debian:~# apt-file find libmagic.so.1
libmagic1: /usr/lib/x86_64-linux-gnu/libmagic.so.1
libmagic1: /usr/lib/x86_64-linux-gnu/libmagic.so.1.0.0
root@debian:~#

Here is an example of installing a package that contains the missing library:

root@debian:~# apt-get install libmagic1

More Information

If you need assistance, you are welcome to open a support case with us. It will help if you can provide us with the following additional information.

Log in to shell as root and save the output ofthese commands:
 

dpkg -l
cat /etc/*release