Somewhat not Veeam related, but I figured there is a good group of folks in here to ask. Earlier we were discussing the largest VM’s we backup in VBR, and I noted that I was looking for maybe a solution to for offloading large amounts of archive data to Wasabi, but still wanting to access the data as a share. I sent a quick message over to my Wasabi rep and he referred me to the Wasabi Cloud NAS service which I do actually remember hearing about a few weeks ago but forgot about. Does anyone have any practical experience with it?And to keep it Veeam related, I was going to ask if anyone had any experience with how to back the service up, although when creating this post, I got a suggested topic…..which is only 6 days old and yet I missed it!But protecting 50TB of data is pretty expensive when using NAS backups, and for archive data that rarely access, so I’m thinking deploy the Veeam Agent for Windows on the server and backup up that volume that way…..though it would need to be teste
I’m going to be likely setting up a new client on a VBR VM with a local NAS as their primary repository (I know...I’d rather do a purpose-built physical server but cost is an issue) and Wasabi object storage for an off-site copy (and likely replication to 11:11 Systems VCC for DR). I’m curious now that we have backup to object and copy to object capabilities, what you folks are doing for that second copy? Traditionally I obviously have used a SOBR using Wasabi as the capacity tier in Copy mode (move mode disabled *usually*, but I just noted that I’m performing copy and move for my internal server) so that I had the data in both locations. However, now that we can backup and copy direct to object, curious if anyone has abandoned the SOBR and are instead using a copy job to send data to the object storage and are keeping the data there with the traditional copy job managing things. @Nico Losschaert posted a debate about the pro’s and con’s of this a couple years ago at the below link,
Came across a new error a bit ago within the Veeam Agent and I’m sharing this for my future self (and anyone else). If all of the actions I performed took care of the issue, or if it it was just a single item, but here’s what I had to do for the below errors. The Errors10/18/2023 1:35:22 AM :: Data Partition (F:) (604.9 GB) 342.2 GB read at 69 MB/s10/18/2023 3:00:25 AM :: Error: The device is not ready. Failed to schedule asynchronous read operation Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Unable to retrieve next block transmission command. Number of already processed blocks: [1402697]. Failed to download disk '0f9d11e0-8171-459b-819c-ebf55d31c45c' The Actions/ResolutionIn my case, researching this error indicated there was an issue with the volume, possibly with a disk table not matching the actual size or something along those lines. It was indicated that I should try shrinking the volume. There
Hi all, last week I deployed a new storage array. I’ve migrated all production VM’s as well as replica’s that resided on the datastores, except for CDP replica’s. I cannot for the life of me figure out how to migrate the CDP replica’s and update the CDP policy to point to the new datastores. Storage vMotion inexplicably gets cancelled by a user later on - assuming that’s VBR even though I currently have the policy disabled. That said, I can’t modify the specified datastore below as well - all is disabled. I thought I might clone the policy, but it looks like CDP policies can’t be cloned like backup and copy jobs - not a big deal but also caught me off-guard.So am I missing something, or do I need to recreate the policy and restart replication from scratch?
Just a quick question...I was tasked with restoring OneDrive data from an account for a client that apparently left and the user was deleted, but someone else was accessing the OneDrive data while the user account was still in the Deleted Users status/folder, but once the 30 days elapsed, that data was purged. This client is currently being backed up by Barracuda Cloud-to-Cloud backup (until I get those folks moved over to Veeam) but I noticed that the last backup of the data was before the user account was deleted. Makes sense, but I hadn’t considered that their OneDrive would even be accessible by the other users during that time period if the user/mailbox had been marked as deleted.So my question is, if a user account is marked deleted, does VB365 still backup the deleted mailbox/OneDrive (or can it even do so - assuming that you had that user explicitly specified or had the job set to backup the entire organization, etc) until Microsoft purges that data? I imagine I can test thi
Ran across an interesting quick issue post v12 upgrade. I had a client who I upgraded to v12 (via our Service Provider Console). I had some clients where after the upgrade, some copy jobs were not reenabled. NOTE: The upgrade shows as a success, but if you view the upgrade job details, it does note that the jobs weren’t reenabled. Anyhow, I was poking that clients machine this morning and realized the copy jobs were disabled but also decided to convert them from per-job chains to per-machine chains. I changed the backup repositories to per-machine, but when I attempted to detach the backup job from the restore points, I received the below error message. Veeam error dialog stating “Disable the primary job and all dependent secondary jobs before detaching the backup.” The strange part about this was that I had already disabled the backup jobs, and the secondary copy jobs were already disabled. Thinking that perhaps it was tied to the replication jobs (metadata), I tried disabling
Found a perplexing issue when I was setting up VB365 the other day. I was attempting to set up the Restore Portal in my multitenant environment using Jorge’s guide (for v6 mind you, but close enough) but when I was attempting to create the Azure AD application, I was receiving a pretty non-descript error.Veeam Error: “Failed to create Azure Active Directory application.” A bit of googling didn’t turn up much. After a lot of troubleshooting, I did manage to get an error when attempting to use an existing Application ID that I had renamed/repurposed about an invalid name but wrote it off because it was a strange possible workaround. I thought that perhaps it was a certificate issue, something wrong with the port I was using, REST API settings, etc.So, like any reasonable person, I created a support ticket and gathered logs. Props to support for isolating the issue on first try quickly with the logs provided. And indeed, Azure AD was blocking the application due to an invalid name.
I just got all of our systems upgraded to v12. With that said, I have two clients using hardened repo’s and two different people set them up, neither of them were me, and the system I’m working on now - the engineer that set that up left the company and moved on a couple months ago. I planned on dipping into these a while ago but never had the time and am now thrust into it. And my linux skills are still fairly basic, maybe intermediate at best.So here’s what I have:The configuration, not that I think it matters, but is a Ubuntu VM running on a Synology NAS with a virtual disk mounted to the VM. I upgraded from v11 to v12 but the repository became unavailable during this process. Single-use credentials are in place and I think I’ve mostly got around the learning curve on this, but can’t quite make connections on things.There are two accounts, I’ll call them “repouser” and “admin”. Repouser is the account that should have permissions to the repo at /mnt/veeamrepo/backups. Admin i
I’ve posted this before in a Friday Fun comment a few months back, but I think it bears repeating, especially because Veeam really did save the day, and maybe a few lives as well! Details may be fuzzy, but it’s all true. It’s a long story, so maybe set aside some time for some light reading, or maybe use it as a 15 minute distraction from working so that you can reset your brain. And I hope you learn something too!I’ve been having issues getting this post, so as much as I hate to do it, I’m going to send you over to my blog to view the entire post. Seems like I my have gotten a bit wordy but I’ll give you a preview below. Setting the StageLong, long ago (okay, it was 2020) in a galaxy far, far away (otherwise known as a small rural community in centralish Nebraska), there resides a community hospital who shall rename nameless. We, an eastern Nebraska-based MSP, sourced this new client and it’s looking like the beginning of a fabulous relationship. I arrive onsite on a hot June day
I know it’s late on a Friday, but I wanted to get this out of my head and off my mind before I forgot. For our internal backup infrastructure, I’m the proud owner of a new Dell PowerEdge R550 with lots of space on local disk. It’s going to replace a Synology RackStation that is slowly dying and is several years old. The new server also has dual 25Gb connectivity (and dual 1Gb connectivity) that will allow me direct ISCSI access to our PowerStore 500T array. This server will be the primary backup repository for our primary site. I am aware that if set this server up as a VHR/LHR, I cannot utilize direct storage access because functions required as a proxy server are not available when the server is hardened. If I choose to forgo the direct storage access capabilities as a proxy server and move forward with a LHR, are there any caveats of using a LHR as your primary repo? I don’t really NEED direct storage access. There’s not that much data to backup every day, and I can still use
Just so nobody is caught off guard, Wasabi announced a rate increase on Object Storage pricing a week or two ago from 5.99/TB/Mo to 6.99/TB/Mo for Pay-Go and new RCS accounts on Aug 1. (increasing on Oct 1 for existing RCS accounts). If you’re like me and on the brink of moving to an RCS account from Pay-Go, do it in the next two weeks to capture that extra $1/TB/Mo savings.Still an awesome value either way, but I know more than a few of us use it so wanted to make sure everyone was in the loop.https://knowledgebase.wasabi.com/hc/en-us/articles/15566987584795
The Task at Hand, or the problem to solveAs a service provider that is actively growing our BaaS offering, one major source or growth is Veeam Backup for Microsoft 365. While it’s relatively easy to understand rental license consumption when backing up VM’s (number of projected workloads * points per license utilized), figuring out how many licenses consumed in VB365 is much more difficult on the surface because, depending on how you’ve selected your objects to be backed up from Microsoft 365 such as selection via groups, you clearly can protect many more objects than you’ve manually selected and consume more licenses. And some objects don’t consume licenses. If you have a dedicated VB365 server for each Organization, perhaps this would be easier. But in my case, we have a single VB365 server orchestrating backups for multiple organizations/tenants. But I need to know how many licenses I’m consuming per Org so that I know how much to bill them, or to make sure they’re within the c
I have a proposal out for a client that want to put their Sage 100/RDS server in Azure and get rid of all on-premise compute. (We’re also migrating their Exchange server to M365).I have proposed a new server, and had planned on backing it up using our VCSP rental licensing and putting an appliance in their Azure to facilitate backups to Blob storage on their account. However, it just dawned on me that I could probably just facilitate backups from Veeam Agent for Windows from this single VM to Blob instead. What would be the preferred/recommended method and are there any special caveats for either that you can think of? I very much live in the on-premise world right now, so it’s all new to me.
After watching last week’s Community Recap, I realized that I missed a great blog posting from @regnor about setting up Wasabi Immutable Storage for VBR. After reading this information, I realized that I, as a smaller service provider and MSP, require a more complex configuration to host multiple tenants in Wasabi and was inspired to share my configuration for setting up Wasabi when you have multiple tenants under one account that you don’t have to have accessing each others buckets.The magic lies in some S3 IAM policy work in place to prevent buckets from being visible and accessible to the wrong tenants. When I was setting this up, there wasn’t much information for doing exactly and S3 policies were completely new to me. Using Wasabi’s and Veeam’s instructions in the links and the end of this post didn’t work for me out of the box, so after asking around in the Veeam Community, R&D Forums and Veeam Subreddit and some experimentation, I was lead to the answers I needed. I hope
I ran several V12 updates through our Service Provider Console and just wanted to make sure that anyone else running these upgrades watches for this issue as well. The issue being, when you push the update and it updates successfully, check the results to make sure that it reenabled all backup and copy jobs at the end. I had a handfull of upgrades where it stated the upgrade was successful, but in checking the logs, the update didn’t reenable a couple of jobs at the end. It seemed to me mostly copy jobs, but I had at least one or two backup jobs as well. Veeam Service Provider Console log results for upgrading a VBR server to v12 that indicated success in the upgrade but failed to reenable jobs afterwords. One other thing to look out for is that when you update, make sure that the client isn’t copying data to a VCC provider that isn’t yet on v12 (looking at you 11:11 Systems/Iland). In that case, copy jobs will now be broken and won’t run until the provider has updated their e
Hey all, I’m just dipping my toes into Veeam ONE and am getting inundated with alerts. I’m sure there’s some fine tuning to play with, but every day when my backups run, I get alerts about suspicious backup sizes. Does this analyze backups from days past, or is there a training period going forward? I’m guessing the former, but I found it strange that for 3 or 4 days now all backups are suspicious.
Service Providers, FYI, looks like licensing is going up slightly for 2023… As we look to close out the year and kick off fresh in 2023, we’re excited to recap some recent Veeam® enhancements and share some future ones. Q1 brought you Veeam Service Provider Console v6, which included licensing and usage reporting integrations to further enhance your Microsoft 365 data protection capabilities. In June of 2022, we kicked off our new partner directory, aimed at driving prospects and customers to our partner community. We’re seeing an average of 10,000+ unique visitors on this page monthly — a huge win for our partners! Our latest Veeam Backup for Microsoft 365 update included integrations and enhancements for our Veeam Cloud & Service Provider (VCSP) community (i.e., Self-Service Restore portal). Speaking of enhancements, Veeam is committed to continuous innovation and has multiple product and platform releases in store to help you grow and scale your business in FY23. A further chang
FYI, for those of you with WordPress sites (looking at you Vanguards, but I’m sure there are others), I came across a nice plugin for backing up to Wasabi. This isn’t really Veeam specific at all, but I figured I’d share anyway.You can find a WordPress plugin called backWPup and create a Wasabi bucket and point the plugin to backup there. Wasabi actually has a page dedicated to it, but honestly, it was so easy to setup, it was probably unnecessary. It can of course backup to FTP, Dropbox, Google drive and such like most apps, and there are probably other plugins that do this as well, but since a lot of folks have Wasabi accounts already, I figured it might be helpful for others if they don’t already have something in place.https://wasabi-support.zendesk.com/hc/en-us/articles/115001900632-How-do-I-use-BackWPup-with-Wasabi-
This little thread got me thinking, and makes me wonder….if you’re tasked with backing up data with a 50 year or 100 year or infinite data retention, this is more than just running a backup and storing it somewhere. Because what good is a backup that is 30 years old if you have no infrastructure to do anything with it? On a somewhat related topic, I once had a client that needed to keep their Dell/Quest RapidRecovery backups for 7 or 10 years. They were looking to move to something like a Dell IDPA appliance (I proposed Veeam with a DataDomain). But the question what, what do you do to keep the servers and MDxxxx DAS’s appliances with the data available for the next 7-10 years? Or do you somehow convert or restore all of the data and move it to your new backup solution whenever there is some sort of major change? And then avoiding bit rot?Hypothetically speaking, or practically speaking for you folks that are tasked with such extraordinary retention policies, what is your plan for
Got caught back up on community recaps last night (I was a couple weeks behind) but over the course of the past 8ish months, I’ve noticed that @Rick Vanover mentions breaking the rule, or not breaking the rule, or sorta breaking the rule but it’s okay. My question is, for those of us who haven’t been around since the community inception…What is “the rule”?
Hey all, my company is using Veeam mostly for our medium-sized clients, but some of our smaller clients with only a few VM’s generally are using something else. A couple with old Datto Siris or Alto appliances, quite a few with Barracuda backup appliances, and even an Intronis client. Most of these clients are paying for more of a BaaS service on a monthly or yearly agreement, though I think a couple actually own their the Barracuda appliance that we sold them in the past.With that said, we’re pretty invested with Datto despite the Kaseya attachment, and they caught the ear of my boss about leasing out Datto Siris 4 appliances to replace all of those non-Veeam clients. That said, I’d rather move them over the the Service Provider side of things and get everything moved into the Veeam house.Here’s what I was thinking. We historically don’t like hosting customer data, and so somewhat in parallel with my developing a VB365 solution for our clients (as most are using Barracuda Cloud-to
I’ve you’ve been following along, Friday Rackspace experienced a major disruption for their Hosted Exchange environment. Why exactly you’d still be using hosted exchange vs moving over to M365 I’m not sure, especially after Exchange has become such a major target for zero-day and ransomware attacks, but there were a lot of folks that still were and they’re hating life about now. Rumor’s I’ve heard indicate that their Exchange servers were not fully patched and malware has taken down the environment. Rackspace as indicated that the outage was caused by a “security incident”.To give a bit if idea just how bad it is, Rackspace is paying for it’s clients to utilize complimentary M365 Exchange Plan 1 licenses to get email up and flowing again, with the intention of moving back after this has been resolved, but I’m guessing most folks will not be moving back - I wouldn’t anyway. Rackspace actually took the hosted Exchange environment offline to try which sounds like ransomware and an atte
I swear I’ve seen some posts about this but can’t find them. I haven’t dipped into the Linux Hardened repo’s with immutability yet, but one of my engineers recently set one up for a client, but as a copy repository. I’m putting together a proposal to replace our internal Synology NAS that is our primary repository with a Dell PowerEdge R550 with a fair amount of local space (8x 8TB disks in RAID 5 or 6) connected via 10Gb or 25Gb links. Backup data is currently copied to a SOBR at a remote site that is using a Synology NAS and Wasabi for immutable object storage. Right now the primary site is keeping 30 days of Forward Incrementals with Active Full’s with no GFS retention, but I plan to ramp up some more retention locally at some point as I ran into space issues a few months back and ended up doing all of my GFS work on the copy repo at the remote site for the time being.Any gotcha’s I should be looking out for this sort of configuration - primarily in regard to using a hardened box
Hey all, getting ready to setup VDRO in the lab and production, but I have questions on the location of the vCenter server. Currently, my vCenter is located in the primary site, but wondering if it should be instead setup at the recovery site, or if I should have HA or ELM configured so that there is a second vCenter setup at the recovery site. ELM doesn’t sound as useful for this situation, but HA may work and there is low enough latency between the primary and recovery sites to support HA. That said, I was hoping to the put the witness at our third site, but latency is higher to that location so that may not work. Anyhow, I know I need to get my VBR backup server moved to the recovery site (was already on my list) but what’s considered the best practice here?
In response to Rick’s posting about liability/supportability of automation desk code...I didn’t respond fast enough to get this in the comments before commenting was turned off…but I rather like this meme I created. Madi, feel free the delete if not allowed.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
