Replies posted by dloseke
I’m very interested in seeing what Object First is doing…...the main issue I tend to have is that I want to have VBR running on a different environment than the performance workload, but want the data to reside on a separate server as well, and want to use Hardened Linux Immutability, which means if I’m using the same server, I’m looking at VM’s, so I need to either store the data in a VMDK which is not advised, or I need to use some sort of RDM which tends to be unsupported on local storage but can be cobbled together. I’m trying to figure out how Object First would fit into that picture and while it doesn’t fix all of my concerns, it sure helps!
Going by my experience, in smaller organisations, there seems to be a preference for a dedicated physical backup server with a Synology or a QNAP for storage. In larger places, especially with those that have the Veeam Enterprise Plus License and storage integration, the backup server is a Virtual machine with a large number of proxies. Yeah, I’ve noticed that as well except I usually see a virtual backup server if a QNAP or Synology NAS (or similar, I’ve seen NetGear ReadyNAS and AsuSTOR as well) is in use for the backing storage. Physical backup servers with local storage can vary in size for sure and in smaller environments as a smaller repo can easily be put on a physical server, up to nearly 250TB depending on disk sizing and RAID type. For instance, on my larger physical boxes, I will use a PowerEdge T640 (in a rack configuration if a rack is available) where I can cram 18 3.5” drives….and with drives reaching 12/14/16TB, in a RAID 6, that nets around 230-260TB. That’s not
I’m not sure I ever really looked, and I’m not sure that I’d want them in there, but is there a capability to push the logs to a Syslog server so that they can feed into our SIEM solution? I guess I do see in VBR some general settings for SNMP, but I’ve never played with those at all.
Hello! Thanks for the share, I was planned to test that today :D ! You beat me to it. That could be usefull for organization with multiple sites and to delegate the access. I really appreciate Wasabi because you can find a lot of documentation with details! Another link: https://wasabi-support.zendesk.com/hc/en-us/articles/360059234472-How-to-separate-access-at-a-Bucket-level I will test this out. I haven't seen this article but looking at the policy I'm not sure if it will list all buckets or list all buckets that the user has access to. If the former, it wont work for me but if the latter.....that'd eliminate the step of having to manually type in the bucket name and would allow the older builds of 11 and also 10 to add the bucket without upgrading. Thanks for sending this link! No problem :D ! I have to find some time to play with this policies too Okay, I tested this and it functions exactly as I had expected...while it doesn’t error ou
Hello! Thanks for the share, I was planned to test that today :D ! You beat me to it. That could be usefull for organization with multiple sites and to delegate the access. I really appreciate Wasabi because you can find a lot of documentation with details! Another link: https://wasabi-support.zendesk.com/hc/en-us/articles/360059234472-How-to-separate-access-at-a-Bucket-level I will test this out. I haven't seen this article but looking at the policy I'm not sure if it will list all buckets or list all buckets that the user has access to. If the former, it wont work for me but if the latter.....that'd eliminate the step of having to manually type in the bucket name and would allow the older builds of 11 and also 10 to add the bucket without upgrading. Thanks for sending this link!
I think this is a classic case of “it depends”. I have SEVERAL clients with virtual backup servers. The thing I don’t like about using virtual backup servers is that more often than not, it’s going to mean that I’m using a prosumer NAS for the backup repository, such as a QNAP or Synology. No battery backed RAID controller, no controller redundancy, possible software tweaks to the software RAID that can introduce corruption, etc.For my clients with physical servers, that means I have a Dell server in place with a battery-backed RAID card, enterprise-grade local drives with enterprise support agreements when a drive fails rather than having to figure out what the current model drive most closely matches the failed drive or figuring out if there is still a warranty from the drive manufacturer, and then finding a replacement while being down a drive for a week or more. For those physical servers, there is the caveat of having some sort of on-host proxy server for VM access, or, my pref
P.S: I am answering so late because I just got this. It seems like (agaaain) I don't receive notifications!!! I think twice in the past two weeks I’ve clicked the Unsubscribe from Notifications link in the notifications email instead of the link to open up a topic…...and then I have to go find the notifications setting again to resubscribe.
I feel like it should be noted that it is this way for every M365 backup product I’ve seen. It does, more or less, incremental backups to grab each file that has been added or changed. M365 backups don’t run in the same fashion of traditional backups like you would use for instance, if you were backing up an Exchange server as a VM, or with an agent even. It’s only looking inside of the mailboxes/OneDrive/SharePoint accounts/repositories for the data that has changed, etc.
Professionally one of my goals is to finish my VMCE certification….still not there yet but I need to do it very soon….should have it done by the end of September. I’m also going to be vetting out some product offerings such as deploying Veeam Backup for Office 365 as a service provider but using Wasabi for the storage, as well as learning more about and probably deploying Veeam Disaster Recovery Orchestrator. As for things I’ve actually completed, I had to do some major infrastructure refreshes at two of our locations and with that I finally have CDP replication running, and it seems to be running pretty well with a 15 second RPO. Quite pleased about that, vs the 4 hour snapshot replication we had in place for the same machines. And we have our backups now copied to Wasabi immutable object storage. I do a lot of the immutable backups for clients, but it seems like our internal stuff always gets neglected so I’m happy to be able to put some focus on that amongst our mass of client
For my customers, they are using 30 or 90 days immutability. GFS retention is keeping much more in most cases up to 1 or 3 years for some depending on how much they are willing to pay, but that’s more of archival of data rather than data recovery. Cost is the primary reason a lot are using object storage over VCC in most cases….they can keep more data for cheaper with object, and they want immutability now. The immutability period is more from a recovery standpoint - assuming they are immutable for 90 days, then that data can’t be touched for 90 days. If I had clients looking for more of an archival function, then we’d be talking about Glacier with immutability or possibly tapes, etc. I have one client that recently started to discern between archiving and recovering data. They have archival VM’s that keep 7 years of data, and those VM’s are backed up to tape and rotated yearly, so at any given time, they can go back nearly 8 years if needed. They were going to try and keep the VM’
You can still update the license key though if you need…..I just ran into this internally. We no longer have an Enterprise Manager but the key we had was managed by the EM. There was a button I could select to still supply the license key as I was changing over to VUL’s from perpetual licensing. I still need to open a ticket with support to get the query to remove the EM entry from our deployment. But that’s the answer…..
I’m pretty constantly revising my own plans for backup architecture. Moving away from Synology NAS’s has been helpful but I was unfortunately down that track for about 3 or 4 years because that was always how we did it, but we finally convinced people to start using purpose-built Dell servers with local storage. That said, getting folks to put the VBR Backup server at the recovery site instead of the primary site has been an issue in some cases, but that’s getting easier. Using REFS was usually not an issue, but I have a coworker that has had issues with REFS in the past and is very afraid of it, and I’ve run into it as well with Microsoft’s various patches that cause REFS volumes to show as RAW, etc.Now I’m starting down the road of the correct architecture for Linux Native Immutable backups. My plan that was down for a client was that at the primary site there is a purpose-build Dell server with local storage. Great. The NAS that they are currently using for primary storage (wi
I have old numbers from my VMCE certification notes that I put into some training materials for when I was training my team, and that presentation is from January 2021, so the numbers have to by much higher by now I would think. This reminds me...I need to actually get around to taking the VMCE exam….. VMCE: 858VMCA: 77
I can’t really speak for backups, but I would assume it would follow what I do with the actual mailbox. Many of my clients just delete the mailboxes so I wouldn’t be concerned with the backups sticking around. If it’s something that they need to keep for archiving or future access by others/replacements, then I convert the mailbox to Shared, unlicense and assign permissions for whomever needs access if anyone, but of course I would still want the shared mailboxes backed up. It’s really a case-by-case of the business need to retain that data, or not.
Hold up…..so are we saying that all VM’s on a licensed socket is covered for agents? If so, I learned something today. I knew about the “up to” 6 free agent licenses with perpetual licensing, but wasn’t aware of all VM’s on a licensed socket being covered for agents. @JMeixner @regnor This behavior changed with v10 or v11 I think. Before that you would have had to license an agent if it's used in a virtual machine. The disadvantage on the other hand is, that you would have to license a whole ESXi host with socket licensing even if there's only a single VM which you want to backup via agent. Okay, fair enough. I came into Veeam 5 years ago with 9.5 U4 but didn’t spend a ton of time with it and got a lot more involved during the release of v10.
Aha, ok, 6 is maximum. Too small for my clusters, I have the maximum with each cluster 😂😂😂 Most of my customers are in the SMB space, so many only have 2-3 hosts in a cluster and use VMware Essentials kits and Veeam Backup Essentials in most cases, so there is a 6 socket max there. Most are licensed perpetual but we’re converting some, obviously selling VUL’s new, etc. We do have two clients on VCSP but rental licensing is more of a one-off for us….used for those few select folks that don’t want to buy or only needed a couple VM’s protected (VBE packs reduced to 5 workloads has reduced that need even more), or for us to use in a pinch when we need a solution right away and the client hasn’t purchased yet.
It is another thing if you want to use an agent on a hardware server, then an instance is used. The socket based licenses have 6 free instances included. So, you can use 6 server agents - or 18 workstation agents. I believe that’s assuming that’s if you have 6 sockets licensed. If you only have 4 sockets licensed, then it’s up to 4 free instances, correct?
Hold up…..so are we saying that all VM’s on a licensed socket is covered for agents? If so, I learned something today. I knew about the “up to” 6 free agent licenses with perpetual licensing, but wasn’t aware of all VM’s on a licensed socket being covered for agents.@JMeixner @regnor
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.