Blogs and podcasts
Bring your knowledge and expertise while creating blogs and podcasts
- 643 Topics
- 5,027 Comments
Wasabi: Minimum storage duration policy
You might or might not know this, but Wasabi does have a minimum storage duration policy in place.What's that?Depending on your pricing model, each uploaded object will be billed for a minimum amount of time.Pay-as-you-go customers have 90 days, reserved capacity customers (pre-paid) will have 30 days.If you delete an object before this minimum duration is over, the remaining time will still be charged.You can find more information on this website:https://wasabi-support.zendesk.com/hc/en-us/articles/360058734492-How-does-Wasabi-s-minimum-storage-duration-policy-work-ExampleYou upload 1TB of objects to Wasabi and have the 90 days minimum storage duration policy in place. After a week you decide to delete the whole 1TB.This means you pay for:7 days timed active storage 83 days timed deleted storageCan I recover deleted objects?You might think, that as you pay for deleted objects, you may be able to recover those. Unfortunately this is not the case, so you can’t use this as a recycle bin.
Veeam Backup for Microsoft 365 - Blog Series - Part 1
For this blog series, I will look at M365, which many people use daily, and why it is necessary to have backups using the Veeam Backup for Microsoft 365. Now my approach will be coming not from a typical user perspective but from an MSP (Managed Service Provider) perspective. I will start part one of this series by going through the shared responsibility model for Microsoft 365 and how Veeam plays a key role there. As we progress through the series, I will talk more about the installation of Veeam for Microsoft 365 and other best practices. Shared Responsibility ModelThe shared responsibility model regarding your data relates to what Microsoft is responsible for and what you as the end-user are responsible for in protecting your data. Many thought that Microsoft did backups for your data, and that assumption could not be farther from the truth. When your data resides in Microsoft 365 as the end-user, you are responsible for backing up your data.What is explicitly each party respo
Get Ready: Enhanced Immutability Monitoring in Veeam ONE v12
One rule of backup is to always have more than one copy of data. This has often been defined as following the 3-2-1 rule, which states, to ensure recoverability in the face of disaster, you need to have 3 copies of data, on 2 different medias, with 1 copy offsite. By following this strategy for backups, businesses gain three different copies of data that they can recover from. However, with the continued threat of ransomware in today’s IT landscape, we need to evolve this rule to meet the challenges that face businesses today. As data is the lifeline for every business, putting in the necessary steps to keep backups protected from malicious attacks is imperative. To do this, having a immutable storage option that prohibits backups from being altered or deleted should be an added element to a long standing rule for backups. With the addition of adding a copy of data that is offline and/or immutable, businesses can ensure that at least one copy is locked from being changed or deleted. H
Veeam Amazing Object Storage Tips & Techniques Part 4
Introducing Veeam’s Smart Object Storage API Veeam Backup & Replication (VBR) v12 which was launched a month ago, has many great features and new capabilities. One of my favorite features is the Smart Object Storage API (SOSAPI). The purpose of this blog is to introduce you to this new and powerful feature.Let’s that off with explaining what the Smart Object Storage API (SOSAPI) is. It is a new tool which allows Veeam and our on-prem object storage partners to develop tighter integrations between our products. So, the great part about the SOSAPI is that a customer doesn’t need to do any additional work to get the benefits of this great addition to the Veeam portfolio. However, you do need to select an object storage platform that has the SOSAPI implemented within their product. When VBR v12 was launched last month, Scality and Object First were the inaugural launch partners for SOSAPI. Cloudian also released a version of their object storage which was integrated with the Smar
[What (else) is new in v12 - 12] - File Level Restore – Compare with Production
A feature that was already available in Veeam Explorer for Active Directory now finds its way into the Windows File Level Restore: Compare with Production. This gives you the option to view the differences between the files in the restore point and the current files in production.After pressing the button, you will be asked for the user with the required permissions.Then you see state for files and directories. What you not see are new files in production that are not in the selected restore point.You can also show differences in file attributes.At least in tested version, this feature (and the following) does not work for Linux.
Veeam Products End of Support Reminder – 2023
It’s that time again to remind everyone that all good things run out of support eventually. The 2023 calendar year has the following products reaching end of support status for the following products.February 2023Veeam Backup & Replication v10 Veeam ONE v10 Veeam Agent for Microsoft Windows v4 Veeam Agent for Linux v4March 2023Veeam Backup for Nutanix AHV v2 Veeam Service Provider Console v4June 2023Veeam Agent for Oracle Solaris v2July 2023Veeam Disaster Recovery Orchestrator v3 (Formerly known as ‘Veeam Availability Orchestrator’)September 2023Veeam Agent for IBM AIXDates To Be Defined:Veeam Backup for Microsoft 365 v5 (Formerly known as Veeam Backup for Office 365) Veeam Backup for AWS v4 Veeam Backup for Microsoft Azure v3 Veeam Backup for Google Cloud v2As a footnote to this section, why do I say ‘dates to be defined’? This is because Veeam’s support for these products is based on ‘Next GA Date + 1 Version’ for the cloud protection products (AWS/Azure/GCP), and ‘Next GA date +
[Quicktip] Enterprise Manager v11 shows latest file version only
I hope, this post safes you the time I spent to figure this out.Normally I do not install Veeam Enterprise Manager (EM) unless there is a use case - like indexed file search. With it, EM can search a index - created at backup time. So no mount of restore-points is necessary to find files in backups. For more information see here:https://helpcenter.veeam.com/docs/backup/em/understanding_search.html?ver=110According to my knowledge, index search is able to lists all file-versions in selected time range. For this you have to filter your search:ProblemIn multiple VBR v11 + EM environments I had the situation that index search results shows just latest file version in result. I spent some time to troubleshoot, ask colleagues, recherche. Finally I get an answer in R&D forum:https://forums.veeam.com/veeam-backup-replication-f2/search-not-behaving-like-i-would-expect-t72642.htmlShort answerIndexed search should show all file versions. This feature is broken in v11 and will be fixed.
Veeam and Tape II: Moving a tape library with data from one VBR server to another
In part I of this series we have seen how to move a tape library with all data to another VBR server which has already data on it.https://community.veeam.com/blogs-and-podcasts-57/veeam-and-tape-i-moving-a-tape-library-with-data-from-one-vbr-server-to-another-1654 The open question was, how do I get my tapes with data to the correct media pools without losing my data…When you select to move a tape to a media pool the following message appears:So, the tapes are marked free, and the data is lost when a tape is moved? A quick check of the helpcenter and the forums says exactly this…https://helpcenter.veeam.com/docs/backup/vsphere/moving_tapes_to_custom_pool.html?ver=110But is this correct?Fortunately, it is not. The tape is marked free when it is moved, but the data on the tape is not lost. Its metadata is deleted from the Veeam database – and this can be recreated. All the tapes from the new library are assigned to the pool “Imported” Move the tapes to their corresponding media pools.
Does ESXi host survive persistent boot device loss?
Yes, it is no backup topic. But because we discussed a reason for my testing here already:I thought it could be interesting. In this post I investigate what happens when a VMware vSphere ESXi host loses its boot device. This device is meant to be a persistent device. For non-persistent devices like USB- and SD-card, behavior is quite clear: whole ESXi OS runs in memory, no mass-write operations should be directed to the device. When it breaks, ESXi isn’t missing it and keeps running.With a persistent device I was convinced that ESXi would die when it broke. BUT: ESXi survives. Not such a clean behavior like with non-persistent devices, but it survived. Reason for testingThere is a concrete reason for this testing. I want to answer the question, if it is safe to boot a ESXi host from a single disk. No Raid, just a single disk connected to a HBA. This would be an additional option for ESXi boot device. Why? Because VMware and other server vendors do not recommend to use non-persistent bo
HPE StoreOnce: Immutability with v12
With the newest release V12, Veeam Backup & Replication is now capable of implementing immutability with HPE StoreOnce Catalyst stores. HPE calls this ‘Independent Software Vendor (ISV) Controlled Data Immutability (ISV-DI)’. With this post I want to quickly describe the requirements and configuration steps.RequirementsThere are some requirements, that need to be met in order to use immutability with StoreOnce systems.you need to have a Gen4 StoreOnce system with at least firmware 4.3.2 you need to configure Dual Authorization Maximum ISV Controlled Data Retention needs to be set to 365000 in the StoreOnce Catalyst Store you need to use forward incremental backup jobs and/or enable GFS for Backup Copy Jobs → For more information check the helpcenter Enable Dual AuthorizationWith Dual Authorization certain tasks on a StoreOnce require a second factor before they’re executed. This second factor isn’t a OTP token or something similar but rather a second user/password which you need to
Veeam Vanguard Nominations for 2023 are Now Open
The Veeam Vanguard program is one of the best influencer/evangelist programs out there, and one reason you need to nominate yourself or someone else that deserves to be in this program. You will gain access to cutting-edge technology as well as resources. With 2023 just around the corner, now is the time to consider nominating yourself or someone you know who should be considered. Also, at this time, for the existing Veeam Vanguards like myself, it is renewal time to ensure I am selected for another year in this exciting program.Being a Veeam Vanguard means being part of an exclusive community of top IT professionals and thought leaders worldwide. As a member, you’ll have access to a wide range of exclusive resources and opportunities, including:Early access to new Veeam products and features Invitations to Veeam-sponsored events and webinars Opportunities to provide feedback and input on Veeam product development Access to the Veeam Vanguard private community, where you can connect
HPE brings LTO-9 to market
New LTO-9 for HPE products are available:LTO-9 is available as of January 10, 2022, for the following entry and mid-range HPE StoreEver solutions:HPE StoreEver LTO-9 45000 internal and external standalone tape drives HPE StoreEver MSL 1/8 autoloader HPE StoreEver MSL 2024 tape library HPE StoreEver MSL3040 tape library HPE StoreEver MSL6480 tape library https://community.hpe.com/t5/Around-the-Storage-Block/Great-news-for-the-new-year-LTO-9-comes-to-HPE-StoreEver-tape/ba-p/7157794
Breaking the Consolidation / Merge Stalemate – For VMware vSphere & Microsoft Hyper-V
Alt Text: Header Image with the text “In the Lab With: Veeam”, subheading “Breaking the Consolidaiton/Merge Stalemate For VMware vSphere & Microsoft Hyper-V”Have you ever seen a snapshot/checkpoint fail to merge? Maybe VMware vSphere was telling you that a virtual machine required consolidation, or Microsoft Hyper-V reported that the checkpoint couldn’t be merged. Whatever the reason, it’s a painful situation.Or should I say, it’s a painful situation, ONCE you notice! And IF you don’t, you have a disaster approaching. Why Snapshots/Checkpoints are bad in the long-term If you need bringing up to speed as to why we don’t like snapshots/checkpoints sticking around, here’s the non-exhaustive, good to know key points:Snapshots/Checkpoints make the original virtual disk a read-only file, and all changes from the snapshot/checkpoint creation point forwards are saved to a ‘delta’ virtual disk. This will consume more storage space. Snapshots/Checkpoints cause increased IO penalties, reducin
[Quicktip] "Error in the application" during VM backup
Yesterday I saw the error a second time, so I thought it would be helpful to others to share.Error happens when VBR tries to read vSphere information for the VM to back up. Error says "Error in the application" like you see in the screenshot.After some troubleshooting we found the reason for this. It was because TCP-port 902 was not allowed (in all firewalls) from the Veeam proxy server to the ESXi host that was hosting the VM to back up. After the port was enabled in the firewall(s), backup ran without further issues. Notes:Used ports for VBR see here: https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=110 Vanguard @Cragdoo also shared this error some time ago. In his case the error was caused by a name-resolution problem on a new Linux Veeam proxy server.I hope this post safe others some time when this error appears.
vSphere Clustering Service VMs on Veeam NFS datastore
As you may know, with vSphere 7 Update 1 VMware introduced the vSphere Clustering Service.The plan is to get more independent of vCenter Server for certain cluster features like for example DRS.Where you certainly notice the difference, compared to older releases, are the vCLS agent VMs shown in vCenter.https://blogs.vmware.com/vsphere/2020/09/vsphere-7-update-1-vsphere-clustering-service-vcls.htmlThere's no need to backup them and if you have a current Veeam version (v10a Patch 20201202 or higher), they're are automatically excluded from your jobs.The agent VMs are manged by vCenter and normally you should not need to look after them.Normally…yesterday we've had the case were some of the vCLS VMs were shown as disconnected; like in this screenshot:Checking the datastore we have noticed that those agents VM had been deployed to the Veeam vPower NFS datastore.As this datastore is managed by the Veeam server and can connect/disconnect at any time, it's a very bad location for the vCLS VM
Veeam Immutable Backups with Pure Storage FlashArray//C SafeMode
When it comes to protecting your business against Ransomware, there are three critical components of a successful strategy. Any solution that you're going to rely upon must have all three of these attributes: Simple Immutable Fast The combo of Veeam Backup and Replication alongside SafeMode snapshots on Pure Storage FlashArray//C is uniquely capable of delivering on all three of these critical requirements. SimpleWhen it comes to data protection, it's easy to let your guard down. The best solutions are the ones that don't require constant care and feeding. They are simple to set up and simple to maintain. Veeam and Pure have each built a solid reputation on designing products that are intuitive and easy to use. Veeam backups made immutable by FlashArray SafeMode are "set and forget" simple. This simplicity comes in part due to the fact that you don't have to change a thing about your Veeam deployment to enable SafeMode protected backups. SafeMode protects the entire Veeam Backup Re
Comparative of Compression Backup on v11
Today I coming here for a simple post about compression Veeam B&R. So, I take a short VM Linux running an Active Directory for this. Below you can see a full backup with a compression set up as Optional. And now you can see the same full backup with compression option on Extreme. How you can see the duration time was decrease in almost 20 minutes when I compress backup on extreme option. The target of backup on this example is an offsite repository. It has a low bandwidth if we compare with a local one. So, when we are planning our offsite backup policy, the extreme compression can help to get better times on your backup execution window.
VBR SOBR Capacity Tier vs VBR Copy Job to Veeam Cloud Connect
More and more customers are aware of the fact that 1 copy of their backups is not longer enough . Yes!I always recommend to my customers and colleagues to implement the golden rule 3-2-1-1-0 (see my blog post : 3-2-1-1-0 Golden Backup Rule | Veeam Community Resource Hub).The thing I want to highlight is having 1 copy offsite and being airgapped - immutable at the same time! Veeam delivers here 2 important possibilities : using a copy job to a service provider offering VCC using object storage with the copy mode in the SOBR capacity tierIn this post the move mode in the SOBR capacity is being ignored.Also using an object storage appliance on-premises is being ignored. The purpose of this post is knowing the similarities and differences between the two possibilities I already mentioned. Why? Because customers and colleagues often ask me why they should choose a copy job to our VCC instead of using object storage at a public cloud provider like Azure or Amazon.I have a list of 10 simil
[New] Grafana Dashboard for Veeam Backup for AWS v3
Greetings friends, today I bring you a new entry about Grafana and Veeam, which I'm sure you'll like and I hope you'll put it in your collection. Veeam has recently announced Veeam Backup for AWS v3. Among the many features included in the product, in v3 it is possible to protect RDS and VPC, as well as EC2 instances, of course, one is a public RESTFul API that has been updated to v1.1, and I thought it might be a good idea to create a Dashboard for this solution.Today, I am pleased to bring you a complete and finished Dashboard for monitoring Veeam Backup for AWS, with no limit of VMs, jobs or Repositories.You will be able to see that there is a Map inside the Dashboard, and that is because I consider very important to be able to look globally and see what regions we have with unprotected VMs. Dashboard for Veeam Backup for AWSWhen we finish the entry we will have something similar to that Dashboard that will allow you to visualize:I leave you a video summary if you want to see a litt
Designing Meaningful Recovery Point Objective & Recovery Time Objective Policies
Today, I’d like to talk about creating and scoping realistic and enforceable RPOs and RTOs for your Business Continuity (BC) and Disaster Recovery (DR) policies and Service Level Agreements (SLAs) within your organization. As every organization will have different requirements the focus of this blog post is on general considerations for shaping your policy.Additionally this blog post is focused around policy design as opposed to backup technologies and should be vendor agnostic for the most part, though where I am aware of features from my backup solution of choice (Veeam of course!!!) I have referenced improvements that solutions such as Veeam can bring to the process.The assumption is made that you’re already aware of the applications, operating systems and data within the organisation/environment you’re designing these policies for. Step One: Define Recovery Priority Before we start to consider recovery point objectives, we should consider the recovery time objectives of our workloa
[Quicktip] Rest root password in VMware vCenter VCSA - since 6.7 U1(!)
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: firstname.lastname@example.org) 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:/
Already have an account? Login
Login to the community
Log in with your Veeam account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.