VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Here is my strategyVeeam Server = Physical or Virtual. Both are fine.Physical is great if you have an Hypervisor/host issue Virtual can be added to SRM / SAN replication to make DR a breeze Virtual is probably going to be cheaper In a disaster as long as I have a windows disk and my backup config I can create a new server quick. Having a second physical server at a DR site with windows preinstalled and not on the domain could save you time in a ransomeware event. Proxies =Physical or Virtual. Physical preferred, both is better.I use Storage Snapshots so physical for fiber connectivity. Physical has an advantage or being able to saturate network / fiber ports without causing issues to virtual environment Virtual are great for hot add. Having a few kicking around is not a terrible idea. Physical is needed to tape In an event where your VMware or Hyper-V environment is ransomewared, you want quick access to a physical proxy.Repos = PhysicalIn an event where your VMware or Hyper-V environm
My biggest vm being backed up was a “Giant” 2TB SQL Server, and a 1.5TB Oracle Server. they were not so big, but very critical, both running in Mechanic Discs, so the backups took so long to perform, and some times, the machines jammed, so they were backed up at night, out of working ours, and every time we did a change, fingers crossed for not messing the Full backup. 😂. I was made aware of an 18TB Oracle backup (with the RMAN plugin) OK, my Oracle databases are not that big. The biggest is around 5 -6 TB. But it is growing 😎 I think my biggest DB server is 14TB. I’m not doing app aware though as the SQL admins get scared when I say I should be taking over their backups.. Even after a demo...
@Chris.Childerhosethanks for the clarification. @Scott I’m having a different password per system with a special pass generator (read: I’m banging randomly the keyboard until 20-60 characters are spewed :D). @Michael Melter“small shops” fits my bill. Specifically the sub organization I’m managing. It’s a 2 person department. However our bigger organization could benefit from a hosted in-premises solution, like bitwarden and passbolt. If I might ask, what is the size of your IT department (approximate order, if you like). I’ve started using KeePass in the way @HunterLAFR uses it at work (single secret file in an onedrive folder, always locally cached between colleagues), while I’ll keep using Firefox Sync for syncing personal passwords there for a little longer. KeyPass was decent for us, but with 1Password using vaults with different permissions settings has been a life changer for our IT deparment, Dev’s have their own vault, apps and web guys have their own, desktop team and then th
Sometimes on support I got customers with VMs around 30-40TB. It's always a pain to troubleshooting problems with VMs like that, I hate. :( Haha, “Will you stay on the phone with me while I restore this?” 🤣😋
I’m so far behind with my company being on prem guardians. This will be a thing before I’m over in Azure.
Recap 100 ideas.-Shoot with a 360 camera so we can watch on VR headsets like we are in the room with you guys. -Big give away.-Get a celebrity to assist you guys.-Do it while skydiving or on a rollercoaster.😂
Well, Just got told I need to add another 50TB to this server, and I have another 300TB incoming, It’s quite critical too. I’m going to have to create a few servers most likely to spread the load, but maybe I’ll do a test in Veeam after to see how long it takes. *Sigh* I’m going to need a few more SANs just for backup data, and a few in production. lol.
Very cool prize \ perk with the VMCE training. Good luck to the selected members!
When I worked at IBM we often had customers drop their maintenance and when things would break the cost for hardware was often 10x to 40x the price of buying it outright. The catch is you cant put the machine back on maintenance until it’s verified no hardware issues are present. The take away is don’t drop maintenance for production machines. That being said, I’ll keep my old SANs around but ONLY for swing space and testing. When I need to pull something from tape to grab a file etc. I usually save the DR SAN as spare parts and provide my own “maintenance” because of my previous experience as an IBM tech. I don’t let other people use it as I can’t guarantee uptime or resiliency, but it works great for temporary space of data that can be lost with no repercussions. (Testing a restore of a few hundred TB is an example) I have so many horror stories from that job of customers losing data. 99.999% of it is usually from a bad decision, improper config, or poor policy. I signed too m
Sockets for my entire production
I cannot see how you are breaking the licensing rule since you are just doing a one time backup of the VMs and then they will not be used again which then shifts the licenses back to PROD for use there. I agree with this. If I were to export the OVF from VMware, and import it to production, that is allowed as well. I’m basically just using Veeam to do this task. It just seems weird, because I’m also technically taking a backup of a VM, where Veeam hasn’t been licensed to the environment, so for a very brief portion of this process, perhaps that wasn’t how it was supposed to be designed. I actually have extra sockets I could attach, however, that environment is so isolated my Veeam server can’t talk to it haha 🤣
Sockets for my entire production Socket licenses could be an issue, because the sockets of the isolated environment are not licences then… With VUL I think it is not a problem... VUL makes sense, however, my production environment is licensed, and the ability to do a storage snapshot on the SAN is allowed. What’s to stop me from moving that volume to my production environment and doing the same thing? or doing a cross vCenter vMotion before backing up the VM? or exporting and importing it. This is why it’s a grey area. Obviously adding a host to Veeam and backing up requires a license, restoring from a storage snapshot that is not mounted to production to production has not come up before. It’s a tricky one. Due to how much we pay Veeam 😀, how many sockets we have, and the fact that these WILL be moved to production, I’m going to go out on a limb and say they will most likely allow it. I would like to hear from Veeam their perspective though. I’m not trying to bend th
The volumes are mapped to a different host cluster on the SAN.Totally separate environment. I recall something about separate clusters can not see a VMFS datastore created on another cluster / vCenter. I tested to see and I was able to map the volumes but it looked like an empty fresh volume with no VMFS datastore in it.
Agreed, I keep old SAN’s for temporary loaners when production has failed and it’s going to be a bit (such as waiting for a new SAN to arrive), lab gear, etc. But once things hit a certain age and lack of support, they shouldn’t be in production. Sure...you might get a few more years out of them….but is it worth the risk to your business and what’s the cost of downtime once you factor in lost revenue, client frustration, and having employees sitting there twiddling their thumbs while they can’t do anything. They are great for personal labs and running I/O meter all day too :)
The volumes are mapped to a different host cluster on the SAN. Totally separate environment. I recall something about separate clusters can not see a VMFS datastore created on another cluster / vCenter. I tested to see and I was able to map the volumes but it looked like an empty fresh volume with no VMFS datastore in it. Okay, yeah, that’d be an issue if the volumes aren’t presented to both clusters. And since the clusters don’t talk to each other, that could be an issue as the second cluster to connect to the volume is going to see those as foreign datastores. I’m not sure off the top of my head if it’s going to like that…..you can probably mount the datastore without resignaturing, but I think you’re really opening up yourself to datastore corruption. Just to test, I spun up a test volume on the the isolated cluster, created a VMFS datastore, created a VM, then unmounted it, attached it to production and as suspected, it showed up as a blank empty dat
Sockets for my entire production Socket licenses could be an issue, because the sockets of the isolated environment are not licences then… With VUL I think it is not a problem... This is a good question for your Veeam sales person... To be fair….you could be using a complimentary VUL included with perpetual licensing, which would be a likely loophole where I’d say this would be okay. This won't work unfortunately. When using socket licenses, the free/gifted instances can't be used for VMs. The volumes are mapped to a different host cluster on the SAN. Totally separate environment. I recall something about separate clusters can not see a VMFS datastore created on another cluster / vCenter. I tested to see and I was able to map the volumes but it looked like an empty fresh volume with no VMFS datastore in it. Well it's not a good idea for production use
I’ll have to watch the repost as I got tied up. Just noticed this up there. Thanks for posting.
I’ll have to watch the repost as I got tied up. Just noticed this up there. Thanks for posting. Not a problem. All VUGs will have the YouTube video posted after the recording is made available to me. 😁 Much appreciated hope there is another one shortly.
I created a VM with No OS the other day so with data reduction essentially zero! I just wanted to test mounting a VMFS datastore to see if the VMDK file was still there. 😂 As a windows shop I’ve been giving a bit more to the system disks lately so I don’t really have “tiny” VM’s. I like to increase logging a fair bit for audits so the extra space is nice to not have to shuffle stuff around.
I don’t think it reconnects, but I could be wrong. As far as 300TB, could you break it up into smaller chunks? That is going to take a super long time. What is your target? on prem SAN?
As a long time member of the forums, I do see a lot of community help over there too. But it’s a combo of some support members jumping in as well. Sometimes they will ask for a case depending if it’s essentially someone trying to get a support ticket handled. If you have questions such as needing help creating a script, architecture, understanding of something it is a great place to go. Feature requests are also often implemented if an idea is brought up enough there. Some of the tape support guys have been very helpful to me over the past few years chatting in there. The community hub has a much more relaxed vibe and I enjoy it here. The blogs section is really cool which doesn’t exist on R&D either. I learn a bunch from both sites and use them both to see what people are up to and try and help where I can. I have learnt quite a bit clicking on posts that didn’t seem to involve me at first glance.
If all your data is stored on a VM why not an instant vmdk recovery to the target VM then storage vmotion? I was thinking this also, but then realized he wanted to use file explorer, so maybe he doesn’t want the whole VM, or to skip the VMware portion of things.
I’ll have to watch the repost as I got tied up. Just noticed this up there. Thanks for posting. Not a problem. All VUGs will have the YouTube video posted after the recording is made available to me. 😁 Much appreciated hope there is another one shortly. I am planning for November now for another one. Rasmus keeps bugging me about it. 😋🤣 Nice. Looking forward to see what the topic is.
I did something similar by doing an instant restore from a storage snapshot, then running a Veeam zip the other day. Similar in the way that I was using a backup to present the data and not have to touch production data. I then ran a file to tape job from the running instant restore.
I should see if I can find some time to check this out. Thanks for posting.
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.
