Veeam Backup for Salesforce 3.1
News, guidelines and various community projects
Recently active
Part 3 of the ‘HPE StoreOnce: Immutability with v12’ series is about a small, but very useful new feature. Before going into it, here are the links to Part 1 and Part 2, in case you’ve missed them.Thanks to Federico Venier from HPE I noticed that the latest StoreOnce release 4.3.6 did introduce two-factor authentication!StoreOnce 4.3.6 supports Two-factor authentication (2FA) which provides additional security for users logging into the StoreOnce system, granting clients access to the system only when they present at least two factors of authentication.https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002919en_us&page=GUID-D9CE533F-9920-4656-A77D-4210E4EC56DE.htmlUntil now, an attacker would have been able to cause damage if he got access to the Admin and Security officer credentials. I described this process in Part 2 of the series: Veeam V12: Immutability with HPE StoreOnce - Part 2Now, with 2FA, the security of HPE StoreOnce backup repositories gets a huge boost.Enable T
Rewind about 2 years. We were short staffed (still are), behind on updates and upgrades and trying our best to get rid of legacy and unsecure infrastructure. After months of work, things were getting close to the finish line. Systems were running great and we were feeling quite safe and secure. It all came to a sudden halt when someone said the service desk phone was ringing off the hook and no one could log in. I tried myself, and not only could I not log in, I couldn’t ping or lookup most of the VM’s on the network. I rebooted one of my workstations and received a 169 address. I knew right away I was in trouble. I could tell DCHP was having issues on my desktop, but on my second PC I could still ping most of the servers with static IP’s. This told me DNS was also down. Great I thought at 4PM on a Friday. We continued to do some troubleshooting and it ended up much worse. It turns out someone decided to put a VERY large file in the sysvol folder to replicate it without confirming the
we currently use azure as object storage and would like to achieve immutability on the backups.veeam does not support “out of the box” immutability to azure. i would like to know if any of these would work or if anyone has better ideas.Immutable blob storage on folder level Enable soft delete for blobs (or container) Enable versioning for blobs (or container) Enable point-in-time restore for containers setup Object replication in azure for the storage account thanks
Hello to all,I would need advices from you guys on how to approach to this setup the best way possible.We have two locations. Both locations have 64TB Synology NAS and also on one side we have one additional NAS for air-gapped solutoin. Now we would like to implement cloud storage and want to ask you guys what would be the best solution in configuration of this scenario.Scale-out repository or similar.At the moment we are doing backups on the one location (Vienna, Austria) and doing Backup Copy Jobs via WAN Acceleration to other location (Novi Sad, Serbia)Would like to configure it to best practices and in the most secured way possible.
I’m new to the community and to Veeam.Does anyone know of a report that will show what I listed? Or at least some of it?Server All dBs for the server Backup time Time backup took to run Type of backup Restore points Success, fail, warning Error messages Enabled\disabled jobThanks much and look forward to contributing once I get a handle on using Veeam.-Mark
Hi Fellow Hubians! So can someone explain to me the reason for the upgrade backup chain format?https://helpcenter.veeam.com/docs/backup/vsphere/backup_copy_change_type.html?ver=120&_gl=1*wzxbvg*_ga*MTMwNTg0NDUyNC4xNjg3ODAyODk4*_ga_PMJS81E58L*MTY5MDIyNDYzNS4xMDAuMS4xNjkwMjI1ODYyLjI3LjAuMA As I understand this changes the chain from having one single metadata file to separate for the per-vm backups. I can see this being a good idea from the separate and conquer point of view (or deal with less hassle if one of the metadata files gets corrupted, so if you only have one, it is much less fun) but are there any other reasons for the move?
We are using community edition to backup two VMs. This setup was done by another user, and now we need to move the VM hosting the backup interface to another host.If I am not wrong, the service is actually running on the underlying host which is Hyperv…. What steps do I have to take to achieve this?I am confused if the community edition runs at hyperv level or not. Useful to know in case hosts are terminated
I really struggled with sharing this story because it’s quite embarrassing. But, if it helps 1 person, it’s worth it. And, not all ‘save the day’ stories are about us being flawless Systems Admins/Architects...we are human, but rather how well we’ve setup and configured our recovery processes. Thanks to @Madi.Cristil for prompting me to “go for it” and just share. 😊I did end up saving the day, but it was at the cost of my own initial negligence the issue arose in the first place, albeit an honest mistake. Interestingly enough, a fellow former Veeam Vanguard (now Veeam employee) and I were discussing this very configuration mishap potential via direct message in the Vanguard Slack channel prior to it actually happening to me.CatastropheSo, what did I actually do to cause the catastrophe at my organization? First, let me start by giving a high-level overview of my backup environment. I use physical servers, with Windows OS, as combo Repo/Proxy devices for my backup environment. I also u
Hi Folks, When I think about being a Systems/Backup Administrator all of these years I can’t single out one single story that fully represents the highs and lows of this profession. So instead I have decided to write a few short sound bytes, streams from moments of memory suffixed with rhymes like one of the those “_restored” attachment names we use in order not to overwrite production. Every moment is also and emotion. We add a taint of emotional metadata to events and memories that we often don’t fully comprehend ourselves. Our work is matrix of puzzles and problems that we face everyday with our silicon little friends. Although sometimes it feels like they are our foes. Gratitude The call broke through the comforting calm silence of a Friday morning IT room like a waiter’s tray that gets turned over in a busy restaurant. An important file was missing. It had been erroneously deleted in one of those careless human moments of blissful neglect. The stakes were very high. First attempt
Morning All Just moving over from Hornet / Altaro to Veeam 12 Community Edition. Set up is in Production have 3 Hosts with 9 VM’s between them. Mainly Server 2016 but one Linux and one Server 2022.All backup every 12 hours onsite and then Backup copy offsite.Offsite copy is onto a different VM Host with enough oomph and memory / storage to run whole lot in an emergency although PAINFULLY Slowly.Anyhow have done a test restore and all Server 2016’s and Linux come up fine (Need a couple of re-boots to recognise new Network etc to talk properly to each other. Server 2022 comes up will not boot due to the Key Protector could not be unwrapped as obviously a different host with different TPM Etc.If I kill the VM but keep the Virtual HDDs and create a new Virtual machine with same settings it all works but is there any way round this?
Happy Friday everyone!It’s time to get competitive 😁 What’s the fastest backup speed you’ve ever achieved with Veeam? I was working with a system recently that wasn’t using any flash within the backup repositories, but beefy RAID controllers and multiple RAID 60’s, and saw a pretty impressive 3GBps throughput at a job level. Sure it’s not NVMe speeds, but it’s certainly no slouch! And I can’t talk about this subject without bringing up my favourite ever UI Bug within Veeam, when I ‘achieved’ a speed of ~429.49PB/s 😂On your marks… get set… post!
This week @Madi.Cristil and El Rickatron are back at it in normal circumstances; however I think the heat is bothering Madalina! Stay cool, Madalina. Watch this week’s recap here: The Linksvia @marco_s via @Luiz Eduardo Serrano via @atinivelli Special Department Newsvia @safiya → Congratulations on launching the Veeam User Group Egypt with @mhmdadl If you are using the Veeam backup for the public cloud products, maybe do an update per this KB: KB4471: Veeam Backup for Cloud Solutions Potential Data LossAlso, big news from Microsoft Inspire this week. Check out my blog: What you need to know about Microsoft 365, Syntex, and Veeam for 1 more reason to back up Microsoft 365.Who’s NewWe welcomed +47 new members this week! But we really want to know @Lionel THIERY - why do the French always ALLCAPS the surname?The coolest usernames are: @Beppe00 @Neto @Deep and @SpicyNudle And Alfred’s pick is @clownyboots178 And a big welcome to everyone else! We will have a special SysAdmin Day stream n