vBrain.info http://www.vbrain.info Austrian Virtualization Power Thu, 14 Jun 2018 16:52:59 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.6 http://www.vbrain.info/wp-content/uploads/2017/09/buysellad_icon-150x150.jpg vBrain.info http://www.vbrain.info 32 32 50840897 Backup Interoperability Matrix Major Update 2018-06 http://www.vbrain.info/2018/06/14/backup-interoperability-matrix-major-update-2018-06/ Thu, 14 Jun 2018 16:52:59 +0000 http://www.vbrain.info/?p=4370 It’s been some time that I have updated the Backup Interoperability Matrix. My thought was that I should wait until there are more vendors supporting vSphere 6.7. In the June update the following backup...

The post Backup Interoperability Matrix Major Update 2018-06 appeared first on vBrain.info.

]]>
It’s been some time that I have updated the Backup Interoperability Matrix. My thought was that I should wait until there are more vendors supporting vSphere 6.7. In the June update the following backup software was updated:

  • VMware vSphere Data Protection 6.1.8
  • Veritas BackupExec 20.1
  • Veritas NetBackup 8.1.1
  • IBM Spectrum Protect for Virtual Environments 8.1.4.1
  • HP Data Protector 10.04
  • CommVault Simpana 11.0 SP11
  • Hitachi Data Protection Suite 11.0 SP11
  • Veeam Backup and Replication 9.5 Update 3
  • Quest vRanger 7.6.5
  • Nakivo Backup and Replication 7.4.1
  • Unitrends Enterprise Backup 10.1.1
  • Acronis Backup Advanced for VMware/Hyper-V 12.5 Update 3 Build 10130
  • Arcserve Backup r17.5 SP1
  • Arcserve UDP 6.5 Update3
  • HPE VM Explorer 7.0.001
  • Rubrik 4.2
  • Altaro VMBackup 7.6.26
  • Cohesity 5.0.2
  • Vembu VMBackup 3.9.1 Update 1

You can find the latest backup matrix update for VMware here and for Hyper-V here. In this update I have also moved 5.5 to the legacy matrix although it’s not End of General Support yet.

For the next update I try to update the tables to have a better readability. In details that means that I will move VVOL/vSAN related information to a seperate table for a better readability.

The post Backup Interoperability Matrix Major Update 2018-06 appeared first on vBrain.info.

]]>
4370
Windows VM with EFI fails to start http://www.vbrain.info/2018/04/13/windows-vm-with-efi-fails-to-start/ http://www.vbrain.info/2018/04/13/windows-vm-with-efi-fails-to-start/#respond Fri, 13 Apr 2018 07:00:32 +0000 http://www.vbrain.info/?p=4342 I just wanted to share a situation I encountered recently with one of my customers. My customer built a new UAT environment with some hosts and a Pure Storage. They have then deployed a...

The post Windows VM with EFI fails to start appeared first on vBrain.info.

]]>
I just wanted to share a situation I encountered recently with one of my customers. My customer built a new UAT environment with some hosts and a Pure Storage. They have then deployed a Windows 10 VM which was configured with EFI. Installation went smooth but after a reboot the Windows VM with EFI enabled came up with a BSOD and the following message:

The operating system couldn’t be loaded because the kernel is missung or contains errors.

File: \Windows\system32\ntoskrnl.exe

Error code: 0xc0000185

That was really strange so the customer tried to do the same installation in their old environment and there was no problem. They also migrated the VM to the new environment and it booted up normally. But after a reboot the migrated VM shows also the same BSOD. So what was different in these two environments?

UAT OLD
  • HPE servers
  • Netapp storage
  • vSphere 6.0 U3
UAT NEW
  • DELL server
  • Pure Storage
  • vSphere 6.5 U1g (includes the newest Spectre + microcode update)

vCenter Server was running 6.5 U1e which includes the first Spectre update.

So after the customer called me and explained the situation my first assumption was that the Spectre update and the new CPU features (IBRS, IBPB, STIBP) were the problem. The reason for that was because the vCenter was running the first patch for Spectre and the 6.5 hosts the second patch for Spectre. Unfortunately I couldn’t find anything external nor internal.

But what I found was a Case with the same behaviour we encounter which led to the KB article 2137402. There was a situation with Windows VMs using EFI and a EMC XtremIO storage explained. Maybe this could also be the same problem with Pure Storage. But just to be sure I digged deeper and found a more general KB article 2146167. It looks like that the root cause for the problem is a compatibility issue between VMware EFI firmware and the storage array when the SCSI commands the EFI firmware is sending exceeds the maximum I/O size of the storage device.

After having this information it was easy to find a Pure Storage VMware Best Practice Guide. In that guide it is recommended to set the Disk.MaxIOSize from 32MB (default) to 4MB when running EFI enabled VMs.

After my customer has changed the setting he could immediately power-on the Windows 10 VM.

There are still some question I can’t answer yet.

  • Is this only happening with EFI enabled Windows VMs?
  • Is this only happening with Pure Storage and XtremIO or do other storage vendors facing the same issue?

If somebody had problems with EFI enabled Linux VMs and other storage vendors, please leave a comment.

The post Windows VM with EFI fails to start appeared first on vBrain.info.

]]>
http://www.vbrain.info/2018/04/13/windows-vm-with-efi-fails-to-start/feed/ 0 4342
Workstation 14 Upgrade – Authorization Service error 6000009 http://www.vbrain.info/2018/01/15/workstation-14-upgrade-authorization-service-error-6000009/ http://www.vbrain.info/2018/01/15/workstation-14-upgrade-authorization-service-error-6000009/#comments Mon, 15 Jan 2018 08:30:21 +0000 http://www.vbrain.info/?p=4283 My main PC was recently updated to the Windows 10 Fall Creator (1709) release. So I thought it was a good time for a VMware Workstation 14 upgrade. The reason for version 14 was...

The post Workstation 14 Upgrade – Authorization Service error 6000009 appeared first on vBrain.info.

]]>
Workstation 14 upgradeMy main PC was recently updated to the Windows 10 Fall Creator (1709) release. So I thought it was a good time for a VMware Workstation 14 upgrade. The reason for version 14 was that it supports Windows 10 Creator release. For more information see the release notes here. The upgrade went smooth as always but when I tried to start a Virtual Machine I got the following error message:

VMware Workstation failed to start the VMware Authorization Service. You can try manually starting the VMware Authorization Service. If this problem persists, contact VMware support.

I search for the VMware Authorization Services under services and tried to start it manually, but also with no success. I checked the Windows Application and Systems logs and found this:

Application Log

Source vmauthd – Version mismatch with vmmon driver: expecting 329.0, got 308.0.

System Log

The VMware Authorization Service service terminated with the following service-specific error:
%%6000009

I also check the VMware communities and found a hint which states that the vmmon driver is implemented through the vmx86.sys file located under C:\Windows\System32\drivers\. I checked the file details and found this:

As you can see the file was not updated during the Workstation 14 upgrade. That now the reason why the VMware Authorization Service can’t start.

How to fix this?

This problem was easy to fix. Follow the following steps:

  1. Configure vmx86.sys to not load during windows boot. To do this use either SysInternals Autoruns (uncheck vmx86 under Drivers) or Registry Editor.
  2. Reboot Windows.
  3. After the reboot rename vmx86.sys under C:\Windows\System32\drivers\ to vmx86.sys_old (or whatever you prefere).
  4. Run a VMware Workstation Repair Installation
  5. After another reboot check again the vmx86.sys which should look like this

I hope this will help everybody who also encounter this problem.

The post Workstation 14 Upgrade – Authorization Service error 6000009 appeared first on vBrain.info.

]]>
http://www.vbrain.info/2018/01/15/workstation-14-upgrade-authorization-service-error-6000009/feed/ 13 4283
Merry Christmas – Desaster Recovery with Veeam http://www.vbrain.info/2017/12/31/merry-christmas-desaster-recovery-with-veeam/ http://www.vbrain.info/2017/12/31/merry-christmas-desaster-recovery-with-veeam/#respond Sun, 31 Dec 2017 09:00:31 +0000 http://www.vbrain.info/?p=4287 The Story It was approx. 6am when my little girl woke me up on Dec. 24th, the day we in Austria celebrate Christmas. Just a small side note. Unlike US and other countries in...

The post Merry Christmas – Desaster Recovery with Veeam appeared first on vBrain.info.

]]>
Desaster RecoveryThe Story

It was approx. 6am when my little girl woke me up on Dec. 24th, the day we in Austria celebrate Christmas. Just a small side note. Unlike US and other countries in Austria the christ-child and not Santa Clause is bringing the presents for the kids. You can image how I felt when I was ripped out of a dream/sleep. After she was dressed up I decided to take a little nap on the couch but she insisted that she liked to dance and I should play some music. So I connected to my Sonos but unfortunately none of my MP3s were accessible.

My first thought was that my Ubiquiti update of the UAPs the day before didn’t worked well but I could connect to the internet so that was not the issue. I tried to connect to my Synology DS1515+ but no login showed up. Pinging it showed that it didn’t respond. So I dragged my tired body to the basement and “hurra” my DS1515+ went black. That was really great and all of this happens on Christmas Eve.

Long story short. After some research it looks like that my Synology, which is powered by an Intel Atom C2538 processor, faced the Intel C2000 bug. I also tested the PSU but the fan began to spin so I assumed the power supply is ok. So there were good news and bad news.

Good news

  • I run Hyper Backup on my DS1515+ and Hyper Vault on my backup DS415+. So photos, videos, MP3 etc. are save.
  • I run also a BackBlaze Cloud Backup for my photos archive
  • I already moved some critical VMs (DC, vCenter, PSC, vRealize Loginsight, vRealize Operations) to my 2-node vSAN cluster
  • DS1515+ is covered by 3 years warranty and I bought it July 2015

Bad news

  • My backup DS415+, also powered by the C2538, can maybe fail in the near future.
  • I didn’t move every critical VM to the new 2 node vSAN cluster (Remote Access Server, Veeam Server, CA, 2nd vCenter etc.)
  • Services like Plex and Sonos are currently down at my home

I also opened a RMA with Synology but I think the speed this case will be handled during the holiday season will not be that fast. In the meantime I need to restore some of the critical VMs which are not already on the vSAN cluster. But unfortunately also the Veeam Backup Server was one of the VMs I need to recover.

Recover Veeam Backup Server

There are two ways to restore the Veeam Backup Server from a backup.

  1. Use the Veeam Extract Utility
  2. Install a new Veeam Backup Server from scratch

Following I will go through the pro and con of each option.

Veeam Extract Utility

Veeam Extract Utility is a small tool that can be used to extract backup data from a VBK file. You can extract this tool directly from the installation medium. To extract the tool mount the ISO file of Veeam Backup and Replication 9.5, navigate to folder Backup and open VBR-SRV.cab with the zip tool of your choice. You need to extract the following files:

  • extract
  • extract.exe
  • veeam.backup.extractor.exe1

To use the GUI you need to rename veeam.backup.extractor.exe1 to veeam.backup.extractor.exe.

Pro/Con

Veeam Extract Utility is a handy tool where you can quickly extract VM data from VBK files. The extracted VM data can be copied to an ESXi datastore and registered to the inventory. The biggest drawback of this tool is that it can only use VBK files. To understand why this is a drawback let me quickly explain the backup methodes of Veeam Backup and Replication.

Forever Forward Incremental

Forever Forward Incremental

When using Forever Forward Incremental, Veeam will create a Full Backup (VBK) on the first run. All subsequent backups are only incremental backups (VIB).

Forward Incremental

Forward Incremental

Forward Incremental is similar to Forever Forward Incremental. The big different is that a synthetic full or active full backup will be created periodically.

Reverse Incremental

Reverse Incremental

Reverse Incremental creates a Full Backup (VBK) on the first run. During subsequent backup sessions Veeam is only backing up changed data blocks. This data blocks will be “injected” into the full backup to rebuild it to the most recent state. In addition to that Veeam is creating reverse incremental backup files (VRB) containing the replaced data blocks from the last rebuild of the full backup file.

As you can see, using just VBK files have the following drawback:

  • Forever Forward Incremental – VBK can be ages old, depending on when the first backup was created.
  • Forward Incremental – depending on how often synthetic full or active full backup will be created (typically once a week) your RPO can be 1 week.
  • Reverse Incremental – looks like the best choice here. But what if the VM was already corrupt during the last backup cycle?

So because of this constraint Veeam Extract Utility wasn’t my choice to restore the Veeam Backup Server.

Install a new Veeam Backup Server from scratch

Because Veeam Extract Utility wasn’t the right tool, I made the decision to install a new Veeam Backup Server from scratch and do a restore from my original Veeam Backup Server.

Pro/Con

Someone could ask “Bro isn’t this a lot of work”. Short answer is “It depends”. In this particular case the answer was “No”. The reason for that was that my main infrastructure was still working, so I had my PSC and vCenter Appliance survided. If the whole infrastructure were down, so no vCenter, no Templates etc. then it would have been a little bit more work because I had to install a Windows VM from scratch and maybe recover PSC/vCenter first.

Fortunately I was lucky because I had a template available on my Backup Synology box. After approx. 30min my temporary Veeam Backup Server was up and running. I added the vCenter to the backup infrastructure and imported the backups from my backup repository. Then I recovered my original Veeam Backup Server. After that it was piece of cake to recover the remaining failed services like my remote access server or the second vCenter for my AF vSAN cluster.

Conclusion

One of my lessons learned was that even when having a backup it can be really complicated to restore individual VMs if the main backup server is affected. With Veeam it was very easy to create a temporary backup server for restoring the most important services. For my future desaster recovery plan I will also include the most underrated/underused feature namely replication to replicate my critical VMs to another Synology box.

References

Veeam Backup method graphs – Veeam User Guide for VMware vSphere

Desaster Recovery graph – https://mapolce.com/tag/disaster-recovery-plan/

The post Merry Christmas – Desaster Recovery with Veeam appeared first on vBrain.info.

]]>
http://www.vbrain.info/2017/12/31/merry-christmas-desaster-recovery-with-veeam/feed/ 0 4287
Backup Interoperability Matrix Major Update 2017-12 http://www.vbrain.info/2017/12/18/backup-interoperability-matrix-major-update-2017-12/ http://www.vbrain.info/2017/12/18/backup-interoperability-matrix-major-update-2017-12/#respond Mon, 18 Dec 2017 08:00:46 +0000 http://www.vbrain.info/?p=4279 In the December update the following backup software was updated: VMware vSphere Data Protection 6.1.5 Veritas NetBackup 8.1 IBM Spectrum Protect for Virtual Environments 8.1.4 EMC Networker 9.2.1 CommVault Simpana 11.0 SP9 Hitachi Data...

The post Backup Interoperability Matrix Major Update 2017-12 appeared first on vBrain.info.

]]>
In the December update the following backup software was updated:

  • VMware vSphere Data Protection 6.1.5
  • Veritas NetBackup 8.1
  • IBM Spectrum Protect for Virtual Environments 8.1.4
  • EMC Networker 9.2.1
  • CommVault Simpana 11.0 SP9
  • Hitachi Data Protection Suite 11.0 SP9
  • Quest vRanger 7.6.4
  • Nakivo Backup and Replication 7.3
  • Acronis Backup Advanced for VMware/Hyper-V 12.5 Build 8610
  • Arcserver UDP 6.5 Update2
  • HPE VM Explorer 6.7.001
  • Rubrik 4.1
  • Altaro VMBackup 7.5.15
  • Veritas BackupExec 16 Feature Pack 2
  • Cohesity 5.0
  • Vembu VMBackup 3.8.0 U1

You can find the latest backup matrix update for VMware here and for Hyper-V here.

The post Backup Interoperability Matrix Major Update 2017-12 appeared first on vBrain.info.

]]>
http://www.vbrain.info/2017/12/18/backup-interoperability-matrix-major-update-2017-12/feed/ 0 4279
Gigabyte BRIX / Intel NUC Gen6/7 – ESXi shutdown issue fixed http://www.vbrain.info/2017/10/28/gigabyte-brix-intel-nuc-gen67-esxi-shutdown-issue-fixed/ http://www.vbrain.info/2017/10/28/gigabyte-brix-intel-nuc-gen67-esxi-shutdown-issue-fixed/#comments Sat, 28 Oct 2017 08:00:21 +0000 http://www.vbrain.info/?p=4210 I bought some month ago three Gigabyte BRIX GS-BSi3HAL-6100 boxes to run vSAN on top of it in my home lab. These boxes were running 24/7 for the last couple of month without doing...

The post Gigabyte BRIX / Intel NUC Gen6/7 – ESXi shutdown issue fixed appeared first on vBrain.info.

]]>
Gigabyte BRIXI bought some month ago three Gigabyte BRIX GS-BSi3HAL-6100 boxes to run vSAN on top of it in my home lab. These boxes were running 24/7 for the last couple of month without doing anything because I didn’t find any time to play with it and put it into “production”. I was also playing with Host Profiles and Auto Deploy which took also some time. In the end I decided to shutdown these boxes to save some money on the power bill. I’m running these boxes without any keyboard or monitor. During the shutdown I realized that the ESXi host was shutdown but the hardware box was still running. Unfortunately when connecting a HDMI monitor to the running box I saw only a black screen. I decided to connect a keyboard and a monitor to one of the boxes to see what was going on during shutdown.

Issue

When I shutdown the ESXi host I got the following message on the screen with vSphere 6.5d and Update 1:

This system has been halted. It is safe to use the reset or power button to reboot.

I also tried to see if this is only a vSphere 6.5 issue or if it’s also present in 6.0 Update 3. With 6.0 Update 3 the “message” was little bit different.

During shutdown the normal DCUI screen was shown and no key was working. The only different was a small different colored “L” in the down left corner of the white frame.

If you were fast at the shutdown and press ALT-F12 you were able to see the last entries in the vmkernel.log.

VMKAcpi: Bus ffff can’t wake system from S5 (max is S4).

This was indeed an unexpected behaviour because I thought it was working when I first installed the Gigabyte BRIX.

Troubleshooting

BIOS downgrade

First I thought that the most recent BIOS update (F5) had some settings which were changed from the previous one (F4). So I used the AMIBCP Bios Editor to check which settings were new and which were old. Unfortunately without luck. Only one Bios setting, which was removed and replaced with a default value in the newest Bios, but nothing else. To be sure I downgraded one of my Gigabyte BRIX to the F4 BIOS but the issue was still there.

BIOS settings check

I also went through all the BIOS settings which can lead to the message “VMKAcpi: Bus ffff can’t wake system from S5 (max is S4).” But I was here also out of luck.

Reach out to Twitter

I reached out to Florian Grehl (http://www.virten.net/) who is the Intel NUC Homelab Guru and he also told me that he has the same issues with the latest Intel NUC Generation 7. Unfortunately he had also no fix for this issue. During this conversation also Mads Fog, Christian Parker and Mehdi Khodaeifard told me that they have the same issue with their Gen6 and Gen7 NUCs. Florian has also a very good post about the Kaby Lake NUC here but also there in the comments, people having the same problem but with no solution.

Downgrade from vSphere 6.5 to 6.0 Update 3

One of my troubleshooting steps also includes downgrading 6.5 to 6.0 Update 3 to see if this issue also happens there. To my surprise in 6.0 Update 3 this issue doesn’t exist. During this step I didn’t know that I have already changed something which has fixed my problem. This was the reason 6.0 Update 3 was working.

Reaching out to William Lam

When you are out of ideas the last hope you will get is from the awesome William Lam. I reached out to William internally asking him for help. He pointed me to another colleague and told me I should open a Case and upload all the required logs from 6.5 and 6.0 so GSS can check which settings are different between the working 6.0 installation and the non-working 6.5.

Solution

When William told me to open a case I created a support bundle from the working 6.0 Update 3 host. After I got this bundle I installed 6.5 Update 1. To my surprise this was working now too. I thought “Great. I’m back where I started”. Now I took the USB drive where the original 6.5d was installed and also this was working now.

I checked the other boxes if they were also working now but “thanks god” both of them still had the issue. So what did I changed in the last hours that could fix the problem. As far as I can remember I changed the following:

  • Created a VMFS volume and redirected the log files there
  • Bios setting “Onboard Audio” to Enable

To evaluate which of these settings was the fix I redirected the log files from the VMFS volume back to the /scratch/log. Afterwards I deleted the local VMFS datastore. After the ESXi restart and shutdown the problem was still not there. So the next step was to disable the “Onboard Audio” again and to my suprise the problem is back again.

I also checked this behaviour with 6.0 Update 3 and 6.5 Update 1 and in both cases disabling the onboard audio led to this issue.

Unfortunately I can’t tell why disabling the onboard audio leads to this issue. In addition I can only confirm that this is the fix for my Gigabyte BRIX boxes. I don’t know if this is also the fix for the Intel NUC Gen6/7. So everybody who has currently the same problem, please check if you also have “Onboard Audio” disabled.

Here is a screenshot where you can find the settings on the Gigabyte BRIX BSi3HAL-6100.

If you have some feedback to this post or info about the Intel NUC Gen6/7 fix please leave a comment.

Update 2017-11-03

It looks like that this fix is specific for the Gigabyte BRIX. It looks like that the Intel NUC Gen6/7 have another problem.

Update 2018-04-27

It looks like this problem was solved in vSphere 6.7 for the NUCs.

The post Gigabyte BRIX / Intel NUC Gen6/7 – ESXi shutdown issue fixed appeared first on vBrain.info.

]]>
http://www.vbrain.info/2017/10/28/gigabyte-brix-intel-nuc-gen67-esxi-shutdown-issue-fixed/feed/ 4 4210
VeeamOn Tour 2017 – Vienna Summary http://www.vbrain.info/2017/10/16/veeamon-tour-2017-vienna-summary/ http://www.vbrain.info/2017/10/16/veeamon-tour-2017-vienna-summary/#respond Mon, 16 Oct 2017 08:00:33 +0000 http://www.vbrain.info/?p=4195 As I wrote in my last post Veeam was touring through Austria and one of these stops was Vienna. I blocked this date in my calendar because as a Media Partner I wanted to...

The post VeeamOn Tour 2017 – Vienna Summary appeared first on vBrain.info.

]]>
VeeamON Tour

As I wrote in my last post Veeam was touring through Austria and one of these stops was Vienna. I blocked this date in my calendar because as a Media Partner I wanted to attend. I was really excited to learn a little bit more about their upcoming releases and the other topics sounded also very interesting.

VeeamON Tour began with a warm welcome from Mario Zimmermann, Country Manager at Veeam for Austria and a strategic overview where Veeam was and where Veeam will be heading in the future. This was held very short to give the audiance enough time to hear about all the new technical stuff Veeam will offer in the upcoming release.

Next was Senior System Engineer at Veeam, Hannes Kasparick, who gave us a complete overview about all the new announced features coming with Veeam Availability Suite v10.

What’s new in Veeam Availability Suite v10

Built-in management for Veeam Agent for Windows and Veeam Agent for Linux (9.5 Update 3)

Centralized management for both Veeam Agent will be integrated into the Backup and Replication Console. This should make the deployment of Agents much easier than using other software deployment methods like SCCM or Altiris. During the deployment you can choose between Managed by Agent or Managed by Server.

  • Managed by Agent means that the agent is deployed as we know it for 1.0/1.5/2.0 including the GUI so an end user can manage their backup jobs (Notebook user).
  • Managed by Server means that a small thin agent will be deployed to the end device (mostly server OS) and all the configuration will be done in the Backup and Replication Console.

And one of the best things about the build-in agent management is that it will be available with the next Update 3 which is scheduled for November.

Veeam CDP (Continuous Data Protection)

With Veeam CDP, Backup and Replication will get the ability to lower the RPO of a replication job from now 15min to 15sec. To accomplish this, Veeam is using VAIO (vSphere API for IO Filtering) which is available on the VMware vSphere platform (Standard licensing and higher) only. This will remove the need of a snapshot during the replication job because VAIO will intercept and redirect the VM I/O to the replica. As of today this feature will only be available in the Enterprise Plus licensing.

Scale-Out Backup Repository — Archive Tier

Veeam Backup and Replication will also introduce a new Scale-Out Backup Repository type called Archive Tier. This new repository will save primary repository space and minimize costs by using cloud object storage like AWS Glacier, S3, Azure Blob storage or others. There is also currently a cooperation between Starwind and Veeam where you can use Starwind Cloud VTL as local Tape target. From there it will be replicated to S3 and then destaged to AWS Glacier.

Primary Storage Integrations — Universal Storage Integration API

Veeam introduced the first storage snapshot integration in 2013 with the release of version 7.0. The first vendor for storage snapshots was HPE with their StoreServ and StoreVirtual / VSA systems. Every new version Veeam added additional storage vendors to their product. Version 8.0 integrated Netapp, version 9.0 brought EMC VNX, VNX2 and VNXe support and with version 9.5 Nimble storage was integrated. But as you can see only every year or release Veeam could integrate a new storage vendor. That was the reason Veeam will introduce Universal Storage Integration API in their next release. This will be a plug-in architecture where the storage vendor will develop the storage plugin for Backup and Replicaion, Veeam will test it and support it if everything is fine. Because of this change it will be easier to integrate new storage vendors into Veeam. The following vendors will be integrated in the next version(s):

  • 9.5 Update 3
    • IBM Spectrum Virtualize (IBM SVC, Storwize family)
  • v10
    • Lenovo Storage V Series (storage based on IBM Spectrum Virtualize software)
    • INFINIDAT
  • next year
    • PureStorage
NAS Backup Support for SMB and NFS Shares

One of the most awaited new features for the new v10 release is NAS Backup support for SMB and NFS. As far as I understood there will be new Veeam proxies specific for SMB/NFS backups which will have an universal SMB/NFS client for backing up the NAS data. In addition Veeam will also support NDMP as protocol for NAS backups. Backups for NAS will not use the classic Veeam container format, it will introduce a new container format which will be optimized for files. Also the metadata and catalog database will not be a MSSQL server because they need a database that is optimized for file search.

Veeam ONE

When Veeam Availability Suite is purchased there is also Veeam ONE included. Currently Veeam ONE consists of 3 tools. Veeam Monitor, Veeam Business View and Veeam Reporter. In v10 Veeam Business View will be moved to Veeam Monitor. Also the following features will be included in Veeam ONE v10:

  • Service and Process Monitoring including actions like e.g. What should be done if a service is down.
  • Backup Infrastructure Audit – Create Audit Report
  • DSGVO support
Oracle RMAN Integration

When speaking with Oracle admins they want to backup their databases with the tools they know, especially RMAN. Therefor Veeam created a plugin which needs to be installed on the database server which will operates as some sort of gateway between RMAN and the Veeam Backup repositories. This plugin will be supported for RAC Cluster as well as for VM and physical Oracle DBs. Restores can be easily done by using Veeam Explorer for Oracle.

One last note from the What’s new was also that there will be Nutanix AHV support in the near future.

What’s new in Veeam Backup for Microsoft Office 365

A week before VeeamON Tour took place in Austria, Veeam released a new version (1.5) of Veeam Backup for Microsoft Office 365. This new version brought the following new features.

  • Distributed, scalable architecture – for enhanced scalability in distributed environments with several Remote Offices/Branch Offices and in service providers’ infrastructures
  • Backup proxies take the workload off the management server, providing flexible throttling policy settings for performance optimization.
  • Support for multiple repositories streamlines data backup and restore processes.
  • Support for backup and restore of on-premises and hybrid Exchange organizations – allows you to choose from a variety of configurations and usage scenarios and implement those that meet your particular needs.
  • Increased performance for restore operations allows for up to 5 times faster restores than in v1.0.
  • Restore of multiple datastore mailboxes using Veeam Explorer for Microsoft Exchange simplifies workflow and minimizes workload for restore operators, as well as 1-Click restore of a mailbox to the original location.
  • RESTful API and PowerShell cmdlets will be helpful for automation of routine tasks and integration into existing or new portals.
  • Support for backup and restore in Microsoft Azure Germany and Microsoft Azure China regions.
  • Many enhancements were made to the UI, including main window, wizards, dialogs, and other elements, facilitating administration of the solution.

What’s new with Veeam Agents for Windows and Linux

As I said before central management for the Veeam Agents will be released with 9.5 Update 3 which is as far as I heard it November. So only a few weeks left and we can see the new shiny feature for Agent deployment.

Veeam Agents comes in 3 license packages:

  • Free
  • Workstation
  • Server

An overview and feature list of each license can be found in this paper for Windows and here for Linux. One new feature of the Veeam Agent for Windows will be the Cluster Support (WSFC and all AlwaysOn clusters) in the Server edition. This will allow you to backup all WSFC based Windows clusters as well as SQL AlwaysON or Exchange DAG. Currently all of these are not supported or only partial support. For more infos see this KB article.

Another feature of the new version is that it will include a “Change Block Tracking” driver. Currently the agent can only to CBT through Master File Table (MFT) analysis which is only working for NTFS. Unfortunately I forgot the real use case behind the driver but I would assume to also support other file systems like ReFS etc.

When the new version is released I will do a separate post explaining all the new features.

For everyone who are using Linux in their enviroments in the new version (2.0) of the Veeam Agent for Linux the following features will be included:

  • Cloud Connect Support
  • SOBR Support
  • Encryption
  • Compiled Kernel Modules

For both Agents there will be also an Agent management from Veeam ONE (monitor and report) and from the Availability Console.

Other topics

Beside the massive information from Veeam about their planed new releases there were also two other presentations from HPE and KPMG.

HPE showed us a part of their storage portfolio which is currently integrated with Veeam like StoreOnce, StoreVirtual (VSA), StoreServ and also their new acquisition Nimble. The interesting part was how Nimble works, will be placed in the HPE storage portfolio and how it is integrated in Veeam through the Storage Snapshots integration.

KPMG has as topic Digital Forensic. Digital Forensic is a really big topic. It goes from classic PC forensic over Cloud forensic to Mobile forensic. Each category needs different tools to get the required information you want. My key take away from this topic was that forensic is very time consuming and for SSDs nearly impossible because of the carbage collection process.

Conclusion

Overall the whole event was a big success for Veeam. There were a lot of people interested in backup with Veeam. I had also good conversation with people I already know and also with new ones like the representative from HPE. I would be really grateful if only half of the attendies would show up at a VMUG meeting. For me the event was also a success because I expanded my network.

If someone is reading this and find information which is not or only partial true, please leave a comment or send me an e-mail and I will correct it.

 

The post VeeamOn Tour 2017 – Vienna Summary appeared first on vBrain.info.

]]>
http://www.vbrain.info/2017/10/16/veeamon-tour-2017-vienna-summary/feed/ 0 4195
VeeamON Tour 2017 – Next stop: Austria http://www.vbrain.info/2017/09/18/veeamon-tour-2017-next-stop-austria/ http://www.vbrain.info/2017/09/18/veeamon-tour-2017-next-stop-austria/#respond Mon, 18 Sep 2017 08:00:38 +0000 http://www.vbrain.info/?p=4159 VeeamON Tour 2017 (english version) VeeamON 2017 took place in the beautiful city of New Orleans and was an awesome conference. If you had the chance to attend you will know what I’m talking...

The post VeeamON Tour 2017 – Next stop: Austria appeared first on vBrain.info.

]]>
VeeamON Tour

VeeamON Tour 2017 (english version)

VeeamON 2017 took place in the beautiful city of New Orleans and was an awesome conference. If you had the chance to attend you will know what I’m talking about. For everybody who couldn’t attend the show this year, Veeam is doing a VeeamON Tour through Europe. One of the stops is Austria where Veeam will play 3 gigs.

  • 10. October – Vienna
  • 11. October – Linz
  • 12. October – Graz

During these half day gigs you will hear about the following topics from Veeam and other experts:

  • Technical sneak peek into the brand new Veeam Availability Suite v10 – New features, best practices and other product updates.
  • Lot’s of face-to-face discussions with your peers and industry experts during the coffee breaks and lunch.
  • Exclusive experience report from customers how they used Veeam Availability Suite to implement their Always-On Enterprise.

In addition to these topics you will learn about the new Veeam Agents, digital forensic and the love between Veeam and multiple clouds (O365, AWS, etc.)

Please join me in this free of charge, short but fully packed half day of pure data protection. Seats are limited so reserve your spot NOW.

At the end of this post you will find the preliminary agenda for Vienna and online registration is available here: VeeamON Tour 2017 Austria

VeeamON Tour 2017 (german version)

VeeamOn 2017 fand im schönen New Orleans statt und war eine großartige Konferenz. Für alle die die Möglichkeit hatten daran teilzunehmen wissen wovon ich spreche. Für all diejenigen die nicht die Chance hatten daran teilzunehmen reist Veeam mit der VeeamON Tour 2017 durch ganz Europa. Einer dieser Zwischenstops wird Österreich sein, wo Veeam 3 Shows abhalten wird.

  • 10. Oktober- Wien
  • 11. Oktober – Linz
  • 12. Oktober – Graz

Während dieser halbtägigen Shows erfährt man von Veeam und anderen Experten Informationen zu den folgenden Themen:

  • Alles zur angekündigten brandneuen Veeam Availability Suite v10 – Neue Features, Best Practices und andere Produktupdates.
  • Interessante Diskussion zwischen anderen Teilnehmern und Industrieexperten in den Kaffeepausen und während des Mittagessens.
  • Exklusiver Praxisreport von Kunden, wie diese Veeam Availability Suite einsetzen, um Ihr Always-On Enterprise zu realisieren.

Weiters wird man auch einiges über die neuen Veeam Agents, digitaler Forensic und der Liebe zwischen Veeam und anderen Cloudprovidern (O365, AWS etc.) erfahren.

Verlieren Sie also keine Zeit an diesem kostenlosen, kurzen, jedoch vollgepackten halben Tag zum Thema Data Protection teilzunehmen. Die Plätze sind begrenzt deshalb melden Sie sich gleich hier online zu diesem Event an.

Am Ende finden Sie jetzt noch eine vorläufige Agenda für die Show in Wien.

TimeTitleSpeaker
08:30 - 09:00Registrierung & Begrüßungskaffee
09:00 - 09:20Begrüßung & Strategische Ausrichtung
Mario Zimmermann
Country Manager Austria
Veeam
09:20 - 10:10Veeam Availability Suite v10 – Neue FunktionenHannes Kasparick
Senior Systems Engineer
Veeam
10:10 - 10:30Kaffeepause
10:30 - 11:00Effiziente und anwendungsintegrierte Speichersysteme für jede Größe und jeden BedarfKurt Mittermüller
Category Manager Storage Solutions
HPE Österreich
11:00 - 11:20Veeam & die Cloud – Office 365, Azure, AWS & Co.Hannes Kasparick
Senior Systems Engineer
Veeam
11:20 - 11:40Digitale Forensik
Michael Meixner
Senior Manager
KPMG Austria GmbH
11:40 - 12:00Kaffeepause
12:00 - 12:50Veeam Agents und ManagementHannes Kasparick
Senior Systems Engineer
Veeam
anschl.Gemeinsames Mittagessen

The post VeeamON Tour 2017 – Next stop: Austria appeared first on vBrain.info.

]]>
http://www.vbrain.info/2017/09/18/veeamon-tour-2017-next-stop-austria/feed/ 0 4159
Veeam Agent for Windows – Backups not working after upgrade to 2.0 http://www.vbrain.info/2017/08/31/veeam-agent-for-windows-backups-not-working-after-upgrade-to-2-0/ http://www.vbrain.info/2017/08/31/veeam-agent-for-windows-backups-not-working-after-upgrade-to-2-0/#comments Thu, 31 Aug 2017 08:00:08 +0000 http://www.vbrain.info/?p=4003 When Veeam released their Veeam Agent for Windows 2.0 on May 11th, 2017 I was first in line to go for an upgrade on my main PC (Windows 10 Build 1607) at home. The...

The post Veeam Agent for Windows – Backups not working after upgrade to 2.0 appeared first on vBrain.info.

]]>
Veeam AgentWhen Veeam released their Veeam Agent for Windows 2.0 on May 11th, 2017 I was first in line to go for an upgrade on my main PC (Windows 10 Build 1607) at home. The upgrade went smooth as I expected from Veeam.

Problem:

When I started my first backup with the new version, the backup job stopped with the following error message:

Cannot request cryptocontainer. Win32 error:The data is invalid. Code 13.

That was not the start I expected from the new version. I started troubleshooting and log analysis of this backup job. Backup job log files are located in C:\ProgramData\Veeam\Endpoint\Backup_Job_HOSTNAME. There you can find the log file Job.Backup_Job_HOSTNAME.Backup.log.

I went through this log and found this:

[15.05.2017 09:25:25] Info <13cc> Requesting cryptocontainer ‘VeeamCryptoContainer’…
[15.05.2017 09:25:25] Error <13cc> Cannot create cryptoprovider.
[15.05.2017 09:25:25] Error <13cc> Cannot request cryptocontainer.
[15.05.2017 09:25:25] Error <13cc> Win32 error:The data is invalid.
[15.05.2017 09:25:25] Error <13cc> Code: 13
[15.05.2017 09:25:25] Info <13cc> Creating cryptoprovider ‘Microsoft Base Cryptographic Provider v1.0’ (0x00000001).. Failed.
[15.05.2017 09:25:25] Info <13cc> Releasing cryptoprovider.
[15.05.2017 09:25:25] Info <13cc> Releasing cryptoprovider.. Ok.
[15.05.2017 09:25:25] <01> Error Cannot request cryptocontainer.
[15.05.2017 09:25:25] <01> Error Win32 error:The data is invalid.
[15.05.2017 09:25:25] <01> Error Code: 13 (System.Runtime.InteropServices.COMException)
[15.05.2017 09:25:25] <01> Error at VeeamEndpointSysUtilsDllLib.IVeeamEpIndexingProvider.InitSecuredStrings()
[15.05.2017 09:25:25] <01> Error at Veeam.EndPoint.SysUtils.CEpGuestSubsystem.GetInventoryInfo(CVssHostInfoConfig config, Boolean secure)
[15.05.2017 09:25:25] <01> Error at Veeam.EndPoint.SysUtils.CEpGuestSubsystem.GetInventoryInfo(CCredentials credentials)

This was now the right moment to open a Veeam Case because the error log contains the same message which also shows up in the GUI. It took only 3-4 days until the Veeam support engineer came up with the right solution and in my case it was not an Veeam issue. It was an Windows issue. I assume this is also specific to Windows 10.

Solution:

  1. Navigate to the C:\ProgramData\Microsoft\Crypto\RSA folder
  2. Rename the folder labelled S-1-5-18 to .old or something else
  3. Restart the system

So what is exactly this S-1-5-18 folder? In my case it was the folder for the well-known security identifier of the “Local System” account. The Crypto\RSA folder stores certificate pair keys for both the computer and users. I can only assume that one of this key pairs was corrupted and therefor lead to this error.

After the system was restarted, backups start working again. I also want to give a big thank you to Mike Powell who was the Veeam Support Engineer helping me with this problem.

This concludes the post. Please leave a comment if you have any further question or feedback.

The post Veeam Agent for Windows – Backups not working after upgrade to 2.0 appeared first on vBrain.info.

]]>
http://www.vbrain.info/2017/08/31/veeam-agent-for-windows-backups-not-working-after-upgrade-to-2-0/feed/ 2 4003
Veeam Agent for Windows: Migrate Agent Backups to Veeam Repository http://www.vbrain.info/2017/08/29/veeam-agent-for-windows-migrate-backups-to-veeam-repository/ http://www.vbrain.info/2017/08/29/veeam-agent-for-windows-migrate-backups-to-veeam-repository/#comments Tue, 29 Aug 2017 15:45:32 +0000 http://www.vbrain.info/?p=3317 When Veeam released their first version of their Endpoint Backup I was hooked. An easy to use client backup tool that can save you from a lot of pain when something goes wrong with...

The post Veeam Agent for Windows: Migrate Agent Backups to Veeam Repository appeared first on vBrain.info.

]]>
Veeam Agent for WindowsWhen Veeam released their first version of their Endpoint Backup I was hooked. An easy to use client backup tool that can save you from a lot of pain when something goes wrong with your client PC or laptop. I started with backing up my primary desktop to a Synology NAS share. When Veeam Backup and Replication 8.0 Update 2 (current version 9.5 Update 2) and Endpoint Backup 1.5 (current version Veeam Agent for Windows 2.0) was released, Veeam introduced the possibility to backup to a Veeam backup repository. In this post I will show how easy it is to migrate any existing Endpoint Backup to a Veeam Backup and Replication repository with your existing backup data.

Veeam Agent for Windows “Shared Folder” Configuration

Currently I’m using the following configuration for one of my client machines.

Because this client does only have one disk, I’m going with the “Entire computer” configuration. For my main client I’m using Volume level backup to select only the OS drive and folders which are important.

At the beginning of using Veeam Agent for Windows I started with using “Shared folder” because I had no production Veeam Backup & Replication in place.

My shared folder is located on my Synology DS415+ in a folder called “Endpoint-Backup” with a retention time of 14 days.

My client backup is configured to start at 8PM and if the client if off during this time it should be backed up once when it is powered on. I also defined that a backup shouldn’t be triggered more often than every 24 hours. That means if I miss the 8PM backup window and the client powered on afterwards it will start doing a backup but it won’t be triggered anymore if I had also selected one of the events (Lock, Log off, etc.).

After the backup was running you can see a backup folder in your destination shared folder called “Backup Job CLIENTHOSTNAME“.

Veeam Agent for Windows “Veeam Backup & Replication Repository” Configuration

When I decided to move from “Shared Folder” to “Veeam Backup Repository” some things needs to be changed in the Agent configuration.

First we need to change the destination of the client backup image to “Veeam backup repository“.

Now we need to define our Veeam Backup & Replication Server. I’m using a specific Service User to connect to the repository. Be aware that per default all Agent access permissions are denied on all backup repositories.

To configure Agent permission on the repository go to Backup InfrastructureBackup Repositories – right-click the repository and select Agent Permissions…

Here you now choose between allow access to everyone, deny access or allow access for a specific user or group.

If the repository permission is configured correctly, only the repositories with the right permissions should show up in the next dialog.

When everything is configured you will see the agent job running in your Backup & Replication Console.

After checking the backup location you will see that a new Agent backup was created. The reason for this is that Veeam Agent for Windows will create a new folder in the root of the backup repository. This is named after the user which was used for the connection to the Veeam Backup Server. In my case the complete path to my backup was “\VBRAIN_svc-veeam-ep\Backup_Job_CLIENTHOSTNAME

Migrating the client agent backup folder to Veeam back repository

If the previous backup chain should be used the following steps need to be done:

  1. Delete the folder of the client machine which was created under the folder USERNAME
  2. Move the previous backup folder to folder USERNAME
  3. Go to the Veeam Backup & Replication ConsoleBackup InfrastructureBackup Repositories, right-click the Agent repository and select Rescan. This should take 1-2 minutes but it will find the moved backup data. CAUTION: If this step is skipped or forgotten the backup will process but create a new backup folder with underscores instead of spaces.
  4. The new backup files will show up under Backup & ReplicationBackupDisk (imported).
  5. Restart the Veeam Agent for Windows backup job
  6. The backup files are now showing up under Backup & ReplicationBackupDisk.

After this procedure the previous created backup files will be used and an increment backup file will be created.

This concludes the post about Migrating Agent Backups to Veeam backup repositories. If you have any questions/feedback please leave it in the comments.

The post Veeam Agent for Windows: Migrate Agent Backups to Veeam Repository appeared first on vBrain.info.

]]>
http://www.vbrain.info/2017/08/29/veeam-agent-for-windows-migrate-backups-to-veeam-repository/feed/ 1 3317