Showing posts with label veeam. Show all posts
Showing posts with label veeam. Show all posts
Monday, April 24, 2017
Tips Veeam problem No disks have been mountedƒ?ÝWindows FLR
Tips Veeam problem No disks have been mountedƒ?ÝWindows FLR
If you are facing problems with Veeam during granulary restore like following screenshots/errors here is relative veeam article that helped us to solve problem:
Here I copy and paste article parts but I warmly suggest to view original veeam article:
http://www.veeam.com/kb1883
<-------------------->
Challenge
When attempting to perform a Windows FLR (Guest Files ?Windows?) the restore fails with:
No disks have been mounted. Either disks of this type aren?t supported or some errors occurred. See log file for details.
No disks have been mounted. Either disks of this type aren?t supported or some errors occurred. See log file for details.
Solution
Confirm that the VM that the files are being restored from was using one the following filesystems.
- FAT
- FAT32
- NTFS
- ReFS*
Troubleshooting Steps
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
1. Clear all temporary files from ?C:Users
Note: When the Veeam Backup Service account is ?local system?, the temporary directory used is C:WindowsTemp.
2. Open an Administrator Command Prompt and run the following commands:
(The the installation path for Veeam if it was upgraded from 6.5 is: C:Program FilesVeeamBackup and Replication)
cd ?C:Program FilesVeeamBackup and ReplicationBackup?
vdk remove
vdk install
3. Confirm that the account being used for the Veeam Backup Service has the "Perform volume maintenance tasks" right assigned to it. This can be located within the group policy (gpedit.msc) under:vdk remove
vdk install
Computer Configuration>Windows Settings>Security Settings>Local Policies>User Rights Assignment
4. Reboot the Veeam serverAvailable link for download
Saturday, March 4, 2017
Veeam B R Excessive workload on Storage during backup
Veeam B R Excessive workload on Storage during backup
Veeam backup can create problems to your storage that is exposed as iscsi/shared folder due to two principal reasons:
1. Concurrent snapshots/Backups that is managed in this section:
2. Excessive storage stress that can be limited here:
3. About hyperV you can revies this screenshot and relative register key:
2 registry values under HKLMSOFTWAREVeeamVeeam Backup and Replication key:
MaxVmCountOnHvSoftSnapshot (DWORD)
MaxVmCountOnHvHardSnapshot (DWORD) registry values
about theory you can review these most exhaustive articles:
Introducing Backup I/O Control in Veeam Backup & Replication
https://www.veeam.com/blog/introducing-backup-io-control-in-veeam-backup-replication-v8.html
VEEAM Invests in Faster & More Efficient Data Protection With Backup & Replication 8
https://blog.workinghardinit.work/tag/backup-io-control/
Available link for download
Sunday, February 26, 2017
Veeam Backup Replication 8 0 Update 3 Released
Veeam Backup Replication 8 0 Update 3 Released
Here they are full release notes and download link (you must register)
http://www.veeam.com/kb2068
To install this update you need to stop "Veeam Backup Service", install update, start "Veeam Backup Service". When you launch Veeam B&R for first time you will be prompted to update Veeam client and any other veeam server repository/Proxy.
Solution
New Features and Enhancements
Microsoft
Microsoft
- Support for Windows 10 as guest virtual machines (VMs), including application-aware processing.
- Support for installation of Veeam Backup & Replication and all of its components on Windows 10.
VMware
- Support for vSphere 6.0 Update 1.
- Added ability to convert "VMware Tools not found" job warning to informational event. To enable this behavior, set DisableVMwareToolsNotFoundWarning (REG_DWORD) registry value to 1.
Linux
- Support for the following additional SSH ciphers: aes128-ctr, aes192-ctr, aes256-ctr, aes192-cbc and aes256-cbc.
Veeam Explorer for Microsoft SQL Server
- Log truncation is automatically skipped for stopped and unsupported SQL Server instances to prevent errors from being logged.
- Preferred network settings will now also apply to transaction log backup jobs.
- Support for SQL Servers using non-standard port number.
Veeam Explorer for SharePoint
- Support for ADFS authentication.
- Support for UPN credentials.
SureBackup
- Proxy appliance will now respond to ping from within Virtual Lab to prevent firewalls automatically blocking its network as public.
Other
- Removed weakly encrypted username and password logging from guest processing components using networkless (VIX) guest interaction mode. Veeam thanks Pasquale Fiorillo and Francesco Ongaro of ISGroup for vulnerability discovery.
- Improved performance of certain user interface operations, such as opening Backups node in large environments.
- Reduced load on SQL Server hosting product configuration database, while improving SQL interaction reliability in large environments.
- Improved performance of configuration backup in large environments.
- Minor enhancements and bug fixes in various product areas.
Available link for download
Friday, January 13, 2017
Veeam and Vmware 6 x CBT problems
Veeam and Vmware 6 x CBT problems
VMware 6.0 has a bug with CBT (http://kb.vmware.com/kb/
However, installation of this fix is not the only action that should be performed to get consistent backups with Veeam or any other backup software.
CBT reset is mandatory for the VMs, and you could do it with help of Powershell script provided by this KB article: http://veeam.com/kb1492
If you do not want to install the patch, CBT should be disabled to avoid any possible issues.
For the Veeam upgrade to version 8 update 3 - it is highly advisable not only in terms of compatibility, but also ij terms of number of varuios fixes and improvements, coming with the upgrade.
We had no issue with disabling CBT other then increased time needed for the backups, therefore I confirm that performance is the only one thing affected with CBT disabled.
Available link for download
Tuesday, January 3, 2017
Veeam B R 7 8 9 stopped to work when renamed server name how to solve
Veeam B R 7 8 9 stopped to work when renamed server name how to solve
With Veeam 7/8/9 B&R stop to work if you rename server.
To restore functionality you need to change and analyze these register fields putting new server name.
I suggest to eviscerate every single key, could you have more subfolder than in my case
HKLMSOFTWARE
VeeamVeeam Backup and ReplicationSqlServerName
VeeamVeeam Backup CatalogCatalogSharedFolderPath
HKLMSOFTWAREWow6432Node
VeeamVeeam Backup and ReplicationSqlServerName
VeeamVeeam Backup CatalogCatalogSharedFolderPath
VeeamVeeam Backup Packages{06C5CCDE-FB93-4566-A13F-75C8A2AFABDC}{564d7967-2024-de0e-f087-bc2e39fba624} ame
Its important that you will change registry keys that are related to sql istances:
HKLMSoftwareVeeaMVeeam Backup CatalogSqlServerName (Should be local)
HKLMSoftwareVeeaMVeeam Backup ReportingSqlServerName (Should be local)
Available link for download
Monday, October 31, 2016
Veeam QNAP and Veeam Deduplication and OffSite Backup Replication
Veeam QNAP and Veeam Deduplication and OffSite Backup Replication
Veeam B&R with Plus license gives the ability to enable Veeam Backup copy feature on differente sites utilizing Deduplication option to minimize Bandwidth usage.
But there is an alternative way to override Veeam Plus licence purchage
You should buy on each site QNAP storage (that has plenty of advantages and very aggressive price) and utilizing deduplication features that this product provides.
Utilizing QNAP as local Veeam Backup repository backup deduplication can work with a remote Qnap with settings that you prefer.
More information about this solution and QNAP features here they are.
https://www.qnap.com/i/useng/business_solutions/con_show.php?op=showone&cid=17
Other blogs articles about veeam and qnap here they are:
Server - how to expose QNAP iscsi storage to Vmware based system
NAS ? QNAP TS-469-PRO-EU Network Storage Server QNAP
All Veeam blog articles:
Available link for download
Thursday, October 27, 2016
Veeam 9 HyperV 2012 R2 and public Lan Fault during backup
Veeam 9 HyperV 2012 R2 and public Lan Fault during backup
During last months we faced a strange problem on Cluster HyperV 2012 R2 VM backup.
Infact, randomly, with Veeam 9 we got a single hyperV public lan to be unreachable causing backup failure (Heartbit lan was working fine)
Here they are actions taken trying to solve issue:
1. When a single host was unreachable with public lan we connected to freeze host using Heartbeat lan via RDP.
We stopped any Veeam processes and services to finish veeam backup (VM was always in backing up mode in HyperV console)
2. There was not any solution to put public lan to working again other than reboot host or disabling and renabling lan connection.
3. Backup faults happened again utilizing Veeam Throttling feature and using windows backup tools indeed than Veeam itself.
4. Finally we suspected that problem was related to lan driver itself.
Searching on internet Lan device name and server model we found that:
HP DL380 Gen8 servers as Windows 2012 R2 Hyper-V hosts and HP Ethernet 1Gb 4-port 331FLR / Broadcom NetXtreme
http://serverfault.com/questions/742520/any-known-fixes-for-hyper-v-host-networking-randomly-stops-responding
What really helped us in our case, was not only to disable the VMQ in all affected Network adapters properties as suggested by Microsoft, but also to disable it in the Virtual machines properties (to uncheck ?Enable Virtual Machine Queue? under each of the virtual machine settings). By default is it enabled.
From Miscrosoft Article:
https://support.microsoft.com/en-us/kb/2986895
Resolution
More information
Set-NetAdapterVmq -Name "NIC 1" -Enabled $False
Set-NetAdapterVmq -Name "NIC 2" -Enabled $False
You can confirm that VMQ is disabled on the correct network adapters by using the Get-NetAdapterVmq Windows PowerShell command.
Note By default, VMQ is disabled on the Hyper-V virtual switch for virtual machines that are using 1-gigabit network adapters. VMQ is enabled on a Hyper-V virtual switch only when the system is using 10-gigabit or faster network adapters. This means that by disabling VMQ on the Broadcom network adapter, you are not losing network performance or any other benefits because this is the default. However, you need to do this to work around the driver issue.
Get-NetAdapterVmqQueue shows the virtual machine queues (VMQs) that are allocated on network adapters. You will not see any virtual machine queues that are allocated to 1-gigabit network adapters by default.
Available link for download
Subscribe to:
Posts (Atom)