Blogs and Podcasts

More en more companies are being a victim of malware, ransomware or even hackers.It is always important to implement the golden 3-2-1-1-0 rule (in detail explained in a former post of me - 3-2-1-1-0 Golden Backup Rule | Veeam Community Resource Hub).Next to this rule, one of the first things to keep in mind is to protect as much as possible your backups because those can save you when you are being attachked and you need them.The first thing that comes in mind, is to harden your Veeam Backup & Replication server as much as possible.I will give you here 10 tips you can implement. There are of course more things possible, but it's a start.1 - Do not domain-join the backup server in the production domainA best-practice is to put the VBR server in a workgroup and not AD domain-joined for smaller environments.Why? If ransomware is nested in a roaming profile of a domain-user connecting to the domain-joined VBR server, this malware can be activated on the VBR server and impact the backup

Why should a customer choose VEEAM Cloud Connect as BaaS with a service provider?10 reasons why it’s such an asset to put a backup copy to a service provider using Veeam Cloud Connect 1 – Offsite backup copyYou all are familiar with the 3-2-1-1-0 golden rule (see my post at 3-2-1-1-0 Golden Backup Rule | Veeam Community Resource Hub), there should always be a backup copy available at an offsite location. Not all customers have the luxury having multiple sites with IT infrastructure available. In that case syncing a backup copy to a Veeam Service Provider is a perfect option having an offsite backup copy available. 2 – Secure end-to-end encryptionBe assured that all data is encrypted at the source (before it leaves the network of the customer), in transit and in storage at the service provider. This without affecting the data reduction ratios of built-in compression. When using a small bandwidth in comparison with the volume of data, a WAN Accelerator is a possible option to use. 3 – Pr

Hi all I hope you all read my post about the 3-2-1-1-0 golden rule - 3-2-1-1-0 Golden Backup Rule | Veeam Community Resource Hub.Perfect in combination with Veeam Backup & Replication to save your backups as good as possible to protect them against ransomware, hackers, ...But what with Veeam Backup for Office 365 ?There is no built-in option for creating backup copy jobs, so there is by my knowledge no option to copy the backups on your primary repository to a secondary repository.I know, Office 365 is running on high-available infrastructure but in case of ransomware or a hacker on your VBO365 server, all your backups can be deleted. So the rule 3-2-1-1-0 should also be implemented in this case.An option could be : create a second job with the same settings as the primary job except writing to another repository. Then you have a second copy of your O365 data. In my opinion that is not a good solution : twice the network-traffic needed (not ideal if VBO365 is running on-premises an

Good afternoon!Though this is a Veeam Community site, not everyone may know, or have heard, Veeam is having their big yearly conference next month - May 25-26 (26-27 APJ). As with last year’s event, this year will also be of the online variety. Hopefully next year we’ll get to meet in person! You may be asking, “why should I attend?” Well, let me provide a few very good reasons why:Knowledge is power! And Veeam will have a lot of it on display via deep-dive sessions and demos. Veeam Solutions Architects, such as Tim Smith, and Senior Director of Product  Strategy @Rick Vanover and his team of amazing professionals will deliver on-point content to help you implement Veeam in your environmet according to best practices and recommendations. What’s New? Every year @Anton Gostev gives his “staple” What’s New session about what you can expect in the next Veeam version release. Though I haven’t seen any detailed schedule or agenda on the VeeamON content, I’m sure this session will still be gi

If you do no know much about Hardened Repository in Veeam VBR v11, read here to learn more about:I was asked, if a hardened repository can be a extent of a Scale Out Repository (SOBR). Good news: yes it can! But you have to take some facts into account.Hardened repositories can be Performance Tiers of SOBR. A SOBR can contain a mix of repositories: ReFS, XFS, Immutable and mutable. Even in mixed SOBR, Performance Placement Policy can be set. That leads to, for example, immutable increments and mutable fulls. When you mix, for example, ReFS with immutable extents, you can use Evacuate backups to free an extent.   I would not recommend any points 1 - 3!In my opinion the point 4 is the most important. With evacuating an extent you can easily migrate from ReFS to XFS with immutability.Notice: If you evacuate an immutable repository, Veeam performs a copy, not a move operation! Which makes perfect sense! When backups are evacuated to a hardened repository, files will be immutable as long as

This short video starts with the 6 reasons why you need an O365 backup, then goes into deployment and setup, followed by how to offer self-service restore for your tenants through Cloud Connect. 

Just wanted to share a VM recovery tip with you all I recently discovered when needing to recover a VM no longer being processed by a VBR Backup Job it was in due to Deleted VM Maintenance Schedule. To assist with my recovery, you have to be utilizing Storage Integration technology with Veeam. My specific environment uses Nimble Adaptive Flash Arrays, so be sure to understand how your Storage Vendor’s snapshot technology works before assuming my “tip” will apply to your environment. Let’s assume you’re backing up VMs with vSphere Tags and during tag maintenance you mis-apply a tag, or forget to (re) apply a tag to a VM needing to be backed up. Or maybe you use vSphere “containers” to back up your VMs (i.e. Datastores, VM Folders), and you mistakingly move a VM out of the Container and the VM is no longer getting backed up. As a good Backup Admin does, such that you are, you review your VBR jobs daily to verify they succeeded: BOOM! Well done, Backup Admin!   But, you weren’t being as t

The following post is not directly related to backup. I hope it is helpful anyway.At a customers backup server a very strange behavior was observed. After a few days without problems, scheduled tasks never seem to get finished. So a current running – never ending – task prevents the next run from starting. A reboot of the server resolved the problem – for a few days.SolutionAfter a research I found out, scheduled tasks get started with a lower priority than interactively started tasks. See my scheduled PowerShell script in screenshot here.Normally this is not a big deal. It does not matter when tasks like reports last longer than manually started. Nevertheless they should at least finish.The solution is to rise the priority of scheduled tasks. Unfortunately this cannot simply be set in the GUI. It can be done in a few steps, I list here.Start Windows Task Scheduler, right-click your task and select Export… and save XML file to a temporary location. Edit XML file with an editor of your

It is not uncommon to reset root password in VMware VCSA (vCenter Service Appliance). This can be necessary when account is locked or password is expired. Normally, you have to shut it down, enter GRUB and edit start parameter to boot into bash. There you can reset root password. Afterwards you boot VM again. Here is the link to this procedere: https://kb.vmware.com/s/article/2147144With vCenter 6.7 U1 it us much easier! Since then it is possible to use a Single-Sign On (SSO) administrator account (for example: administrator@vsphere.local) to login to Appliance Interface (Port 5480) and shell. And exactly this can be used to reset the root password. In short it goes like this: Take a snapshot/backup of VCSA - it is always a good idea to start with a backup  Login as a SSO-administrator using a SSH client or console. Enable and start shell: shell.set --enable true shell Change root password sudo passwd root​​​​​​​​ DoneHere is the link to the more detailed VMware KB-article: https:/

Hi Everyone, I wanted to start sharing some of the content and learning paths I have been taking to get a better grasp on Kubernetes and Cloud Native technologies.   First of all I am going to be putting my learning and findings on this page as I continue to navigate these new technologies.  And then I will keep adding if possible to this post with the latest blog posts.  Part 1 - Choosing your platform Part 2 - Setting up your Kubernetes cluster Part 3 - Playing with stateless workloadsPart 4 - Setting up dynamic shared storagePart 5 - Helm & MinIOPart 6 - Context is ImportantPart 7 - Load Balancing your Kubernetes Home Lab with MetalLBPart 8 – Deploying KubeApps the visual marketplace for all your Kubernetes AppsPart 9 – A Mission Critial App - PacmanPart 10 – Backups in a Kubernetes worldI would love to get your feedback useful links to add or things we should share with the community. 

See here how it works in a step by step guide.To start in Instant SQL Recovery wizard, select your server and choose Restore application items.Here you choose if you want to restore to the latest available restore point, or select a listed one. At the end of wizard press Browse. Veeam Explorer for Microsoft SQL Server starts.Choose the database you want instantly recovered and select to do so. You have these options to choose from: Latest restore point. Point-in-time state. Recover to another server. This you can used to recover DB using a different name while original DB is still in place. In this demo, I selected point-in-time state to show additional options.Select point-in-time state you want recover to.Notice:First option recovers to date and time, recovery point was created. Second option lets you choose the exact date and time to restore to. As noted, transaction log backup is required here. Checking option to restore to a specific transaction, lets you choose a marked tran

Why do you think Veeam is in this place today?   

With the recent topic of how to change the IP/DNS Name of the vCenter recently posted I wanted to share for those with experience in SQL how you can modify the vCloud URL within Veeam.This requires some SQL knowledge and that you shut down the Veeam services during the process.  The main query is as follows:SELECT * FROM Hosts WHERE type=1 OR type=6 OR type=14; Under the "options" column for the relevant row(s) we're going to see the reference(s) to the old cell hostname. Then once you are ready follow these steps:0) Veeam Configuration Backup1) Stop Veeam Services2) Backup VeeamBackup SQL DB3) SELECT * FROM Hosts WHERE type=1 OR type=6 OR type=14;4) Copy the "options" value5) Modify the copied "options" column value to have the new VCD URL6) Note the id column of the related row7) Perform the update query on the objects that need the new URL:UPDATE Hosts SET options='NEW_options_VALUE' WHERE id='ID_FROM_STEP_6';8) Start Services9) Open Console, and "next" through the properties of the

From Veeam Backup & Replication restore Mac OS FileOpen Veeam Backup & Replication console and click Backups, Disk. You will see the Mac Agent Backup. Right-click “Your Mac Device Name”, Restore guest Files, Linux, and other…Select the available restore point.A new feature of v11 is the ability to leverage an existing managed Linux server to act as the file-level recovery appliance, you can choose a Linux host that I have in my environment.v11 will open the Veeam Backup Browser, which enables the ability to see the structure and the ability to recover your files and folders.You can restore folder or file to the v11 Desktop only, If you need direct restore the Mac device, please continue to see “Step by step of Veeam Agent for Mac 1.0 @ Part 3 (Restore from MacOS)” Coming Soon…Reference Link: https://vexperthk.com/2021/03/09/step-by-step-of-veeam-agent-for-mac-1-0-part-2-restore-from-vbr-v11/

Hey everyone,I wanted to share this recent blog post I made with yourselves as whilst it’s not directly related to Veeam, I was helping someone that had locked themselves out of a Veeam database and needed to take a native backup for a support case with Veeam.  I was recently helping a customer create a SQL database backup for a support ticket and noticed that they had an interesting SQL Server configuration. There was only a single account with sysadmin rights, the sa account, but this account wasn’t allowed to sign in. The SQL Server was domain joined but there was just a single group allowed with Windows Authentication and that had the “public” server role only.There are a few reasons this could happen, accidental permission changes, or groups and/or user accounts being deleted from the domain that had been assigned the sysadmin role as examples. Thankfully it’s not the end of the world for you if you find yourself in this situation. Breaking Back into your database! This will invol

Hello There, I just wanted to share an issue I had on one of my customer to avoid others the problem:We setup a standard Veeam Backup & replication Server on a W2019 VM and a Std SQL 2019 on another one to host the DBs from VBR and Enterprise Manager.The DBA from the customer insisted to setup an alias for the DB server when pointing Veeam to its Database server as it’s their best practice to facilitate migration (He was obviously not aware how easy it is to move Veeam Database). So he setup a CNAME that pointed to the real SQL server.The setup went well using the CNAME. We created a “management job” to save Veeam by itself, VBR+SQL servers. The job detected the roles and proceeded as normal but failed on SQL VSS processing. We spent a lot of time to validate that permissions were right (the DBA didn't gave us the sysadmin rights on the backup service account, wise guy) and that the service account on the SQL had the proper permissions too for the VSS writers. Long Story short: I f

Today’s topic will be regarding Cloud Native workloads within Azure & AWS and how best to adhere to Veeam’s 3-2-1-1-0 best practices and how concepts can differ from traditional on-premises data protection. Remember the 3-2-1-1-0 best practice is a minimum desired standard and going above and beyond these minimums will help your data availability and recoverability objectives.The public cloud has provided a huge transformation opportunity for organisations, the pay as you go model enables organisations to deploy quickly and without the overheads of infrastructure management. But these platforms are still part of a shared-responsibility model, with a key risk that you retain being, the protection of your data.3 - Copies of Your DataLets start with the easiest one. Three copies of your data, including your production data. Public cloud services such as Azure will inform you that they retain three synchronous copies of your data as a minimum via their “Locally Redundant Storage” offer

I took the time to create in Draw.io a client scenario., with the 3 cores components Backup Server - Proxies - Repositories would look as follows   Only one with Windows ….      

So, today I’m gonna show you a simple comparison with 1 VM per job versus 2 or more VM per jobs. On my scenario I have 2 VM for my Active Directory environment with 40GB size each.----------------------------------------------------------------------------------------------------------------------------So, in first example I create 1 job per VM: In this shape it consume exactly 40GB on my repository: ----------------------------------------------------------------------------------------------------------------------------In the second example a create a unique job for the same 2 VM’s: And in this shape it consume 37GB on my repository:---------------------------------------------------------------------------------------------------------------------------- How can we see deduplication of Veeam B&R gives a good space on our backups.In this environment was only 2 small VMs, but now you can imagine how this impact an entire datacenter.

Probably the following is widely known. But I did not know up to now and found out today. Maybe it is new for others too.After the Upgrade to v10, suddenly Linux VMs are not getting backed up any more, because defined guest interaction user was domain-based and could therefore not login into Linux VM. So solution would simply be to disable guest processing for this VM. Problem was, VMs were selected by vSphere Tags for this job. Fortunately solution is quite simple:Edit the job and got to Guest Processing and  click Application Here you can see the selected vSphere Tag. When you edit this line, options are set for all VMs this Tag was assigned to. Press Add → VMs and Tags → expand Tag of choice → select exception VM   Select new line and press Edit Set option as desired for this/these VM(s) That's it! This also works for custom Guest OS Credentials: BTW: If you suffer from the same behavior after upgrading to v10 (and probably to v11 as well): Curiously this is not a bug, it is a bu

If you haven’t heard, Veeam Disaster Recovery Orchestrator v4 (formerly known as Veeam Availability Orchestrator) is now available, and better than ever.Now VDRO can orchestrate recovery for 4 types of your protected data:Veeam CDP Replicas - NEW in v4 Veeam Replicas Veeam Backups Replicated Storage Snapshots (NetApp ONTAP and Lenovo ThinkSystem DM)This means you have the ultimate in flexibility and choice when it comes to protecting all of the data in your environment.  From mission critical apps, to those dev environments that would be nice to recover easily but are usually ignored for DR planning purposes, you can do it all with the same tool, the same way.It couldn’t be simpler to create a DR plan in Orchestrator.  Check out this video where I create a CDP Replica orchestration plan, run a readiness check, and launch a failover in less than 10 minutes.There are some subtle differences between plan types, but yes, Orchestrator is really that easy to use. You can even get granular an

Hey everyone!VMware released some unexpected news yesterday regarding the end of support for vSphere & vCenter 6.5 and vSAN 6.5 & 6.6. These were both originally intended to reach End of General Support (EoGS) this year, on the 15th November 2021. VMware are now extending this general support window to the 15th October 2022, no changes to the end of technical guidance have been announced.This date might seem familiar, vSphere 6.7 reaches EoGS on the 15th October 2022, meaning unless you have an extended support contract with VMware, this is the date you will need to migrate away from the vSphere 6.x platform by!VMware have kept things simple by extending the EoGS for vSAN 6.5 and 6.6 to this same date which also coincides with vSAN 6.7 EoGS.In summary, things are a lot more simple, on a vSphere/vCenter/vSAN 6.x release that isn’t already EOL? It will reach EoGS on the 15th October 2022 now.However, like so many freebies, there can be strings attached, such is the case here. So,

This is the second part of my SQL Instant Recovery posts. First part:I would like to list some of the software’s behaviors here.Veeam Explorer for Microsoft SQL Server is closed. One could gain the impression from the documentation Veeam Explorer does the whole work. This is not the case, if Explorer gets closed, just start it again. Mount Server, proxy or repository Server is offline. This is a problem, because these components are necessary for keeping your Instant Recovery database alive. Fortunately Veeam took this into account. So the system checks periodically (every 5 minutes) if needed components are online again and re-establish all connections. If you fixed the problem before next scheduled retry, you can trigger the retry manually by pressing the Retry button.Restoring to original locating with original database still in place. The Explorer wants to have your decision confirmed. Veeam VBR Server uses older SQL Server version than source Server. This is generally not a proble

One of the challenges that I have faced learning Kubernetes is persistent storage. It is a steep learning curve but one of the most essential areas elements necessary to make containers become a real force in the world of computing. There are many flavors of Kubernetes persistent storage and making the right choice for your workload and application s is no trivial matter.Would it not be nice if there was some helpful utility to test and validate my persistent storage setup?Well now there is thanks to Veeam Kasten’s Kubestr!As stated on its web page “Kubestr is a collection of tools to discover, validate and evaluate your kubernetes storage options.”Lets take a look at what this thing can do:You can download Kubestr here: https://github.com/kastenhq/kubestr/releases/tag/v0.4.13 I chose the Linux binary and downloaded to my control node.Untar the the tarball and you are ready to go. In linux make the file kubestr executable by typing in sudo chmod +x kubestr Then run .kubestr and it will

Hello community,I don’t know if this is common knowledge (I guess all the hardcore Windows Admins hanging around here know this), but I think I share this, nevertheless.I have tried to back up a Windows 10 PC with a server managed VEEAM agent for the first time today (up to now there were Windows Server only). In this environment is no Windows Domain present, local users on all systems only.When I tried to connect to the Windows 10 PC from my VEEAM Server to create a managed server the connection was refused. No specific error message, it just failed… OK, I tried to ping the PC and to connect to it, all ok. Then I tried an administrative share and it failed, too. So, it seems not to be a VEEAM Problem, but a Windows problem…I did some internet research and found that the Windows administrative shares are not accessible by local accounts over the network since Windows Vista. OK, this is some time, but… when do you do such a thing?After some more reading I finally found the solution. You