Veeam Community Forums Digest for dandvo [Jan 29

Veeam Community Forums Digest for dandvo [Jan 29 - Feb 4, 2018]

Veeam Community Forums Digest

January 29 - February 4, 2018

THE WORD FROM GOSTEV

Last week, we've launched a huge product licensing change that some of our customers have been asking for – the per-VM licensing option. As you know, previously we've sold our products for virtual infrastructure to end users strictly on per-socket basis. And most customers loved it, because they did not need to worry about the number of VMs they are protecting. But in certain edge cases, such as heavy ROBO environments, this was not a very good deal – as our customers sometimes had to license 2 sockets running just a couple of VMs. On the other hand, from renting the same products to our service providers on per-VM basis, we saw a lot of positive feedback regarding how this allows their clients to avoid upfront costs and get started with minimal investment – as opposed to having to spend a lot of money upfront (aka capital expenditure).

So, we decided to blend the best of both worlds together in the new, per-VM subscription licensing option for end users. You can select any number of VMs – which, unlike with per-socket license, you CAN exceed slightly – and there are 1 to 5 year subscription licenses available with significant discounts on a longer subscriptions, also depending on how you purchase. Another big benefit of subscription licenses is that they already include Premium 24x7 support – whereas with perpetual licenses, you need to pay on-going support and maintenance fees every year. All of these benefits can make subscription a more attractive and cheaper option sometimes, depending on your use case. But of course, as with any subscription, the catch is that you don't own the product forever – as is the case with a perpetual license. The new licensing option is now live on veeam.com (just open a pricing page for Veeam Backup & Replication, Veeam ONE – or any of their bundles). Check it out and as always, do let us know your feedback!

Here are a few fresh security vulnerabilities that made me chuckle. First one is the vulnerability in Kaseya RMM agent that was used to deploy cryptocurrency miner to all those managed computers. How cute – and I guess they users should be really happy as that's really not the worst that could have happened!! And another one is a whole slew of critical vulnerabilities in VMware VDP, providing multiple easy ways to take over the appliance and destroy all the backups. This is by no means to bash the corresponding software vendors – at Veeam, we fixed our own share of reported vulnerabilities (they were just not cool enough to make the news, for now) - but rather to show one simple fact: we're all terribly exposed these days. With the number of criminal hackers growing exponentially following the easy money, cyber-threats will keep escalating to the entire new level, and soon will start consuming most of IT Pro's time. Meltdown/Spectre vulnerabilities were the recent cherry on top, demonstrating that critical vulnerabilities can be found just about everywhere – and the hackers will always be ahead of the game. We just have to accept that they have the edge, and always assume they'll be successful in their endeavor of penetrating into our environments. Needless to say, this elevates the importance of data protection and air-gapped backups to the new heights – but also shows that those new regulations like EU's GDPR could not be more on time, particularly with the requirements like disclosing data breaches as soon as they happen.

I could really have used this awesome tip from my fellow MVP Sami Laiho in anger a couple of years ago, when some Windows patch made my laptop unbootable – but I didn't know it was possible to remove a hotfix from an unbootable OS, so I opted to reinstall one instead. But apparently, it is super easy to do:
1. In the Windows 10 boot menu, go to Repair.
2. Go to Tools > Options to get a command prompt.
3. Confirm the drive letter for the Windows image (usually it is D:\).
4. Run dism /Image:D:\ /Get-Packages to view the installed packages along with their date of install and note the name of the rogue package.
5. Run the following command with the wanted package name dism.exe /image:d:\ /remove-package packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0
Then just reboot the system normally, and you should be good to go!

BEST POST OF THE WEEK

Re: ReFS: Moving Backup Copy Job to new ReFS Repo [BY: adapterer • LIKED: 3 times]

You can accomplish this with Windows Storage Replica if you have datacenter edition - https://www.virtualtothecore.com/en/win ... s-volumes/
Depending on your setup you could use Veeam agent to backup as it works at block level and restore to the new volume - but I have not tested this.

ddprecist

Prohledat tento blog

Veeam Community Forums Digest for dandvo [Jan 29 - Feb 4, 2018]

Komentáře

Okomentovat