Hi again, testers of new technologies in your lab (’cause your boss doesn’t want to jump on the bandwagon🙂). DK here.
I’ve been recently watching some VCP Foundation videos and researching some Microsoft technologies and my question to you is: how the heck can one be an MVP and vExpert at the same time without getting his head exploded?
This week I’m planning on finishing the Veeam’s demo lab and fly to Atlanta for MS Ignite. My part in this lab preparation is mostly setting up Agent For Linux and integration with VBR (yeah, I still remember I have to write something about it). Those of you who have been at VMworld US and have seen Veeam’s lab there, know that I had my hand in that lab!=)
So, if you go to Ignite or VMworld EU, come by to say hi and check out our
free swag lab:
- Veeam B&R 9.5 beta
- Veeam One 9.5 beta
- Veeam Agent for Linux beta 2
- Nimble Integration
- and more cool stuff
Anyway, raise your hands those who like doing the same job twice? Cool, zero hands spotted among all of my five readers. Apparently, Veeam doesn’t want you to do that as well.
If you haven’t been watching for new features of Veeam Backup and Replication 9.5,
shame on you! let me tell you that in my opinion, the integration with Microsoft’s ReFS 3.0 is the most outstanding.
- You have your bits of backup stored as separate files on the disk.
- To merge them into a single file (called “synthetic full backup”), you sequentially copy all the latest blocks of data to a new file.
Anyone sees what’s wrong with this process? If not, read four paragraphs above: you’re doing the same job twice. You already have all the blocks with required data on the disk, so why copy it again?
Imagine if you have a story printed out on a bunch of pages that are out of order. What would you do to make a whole book? Well, according to the BEFORE section, you’ll sit down and start rewriting the sheets from scratch in the correct order. Sounds cool? Don’t think so.
Instead, you can just put appropriate page numbers to show the readers in what order to read them. That’s what ReFS 3.0 integration does.
- You have disk blocks containing backup data.
- To get a synthetic full, Veeam just points to the blocks of already existing data.
If that’s not cool, you can throw stones. Not only it saves time and resources because it doesn’t process and write any additional data, it also saves storage space, because… well, it doesn’t process and write any additional data.
“Yeah, cool story bro, but gimme numbers!” you might say. No problem:
… synthetic full backup being made on a VM backup on ReFS which took only 58 seconds to process three incremental backups. Compare this to over 36 minutes for the same VM backed up to an NTFS volume!
Taken from here. Make sure you get your hands on our demo lab to check that out
If you’re still not impressed, check out the post from Didier van Hoye (Veeam Vanguard, btw!).
So I would say: start setting your clients’ and bosses’ minds for a Windows Server 2016 and Veeam 9.5 update right about now, it’s gonna be super hot.
See you at Ignite!