VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Rasmus, the link for the practice exam was blocked by my browser because it wasn’thttps://rasmushaslund.com/vmce-practice-exam/#vmce-practice-exam.It ishttps://hostfirst.press/vmce-practice-exam/?__cpo=aHR0cHM6Ly9yYXNtdXNoYXNsdW5kLmNvbQ.Not sure why this link is different from the text, but thought you should know. This is the warning I got from NortonLifeLockDangerous Webpage BlockedYou attempted to access:https://hostfirst.press/vmce-practice-exam/?__cpo=aHR0cHM6Ly9yYXNtdXNoYXNsdW5kLmNvbQThis is a known dangerous webpage. It is highly recommended that you do NOT visit this page.
Not yet, but I have a few customers VERY interested and will be testing soon with them. I will update here.
Very helpful page to send all my customers to when they upgrade, which should be very soon. CDP and Hardened Linux Repo are driving my customers to upgrade, and perhaps to purchase. Thank you, Rick!
I was asking this same question recently and did not get any “real-world” responses. I have a customer that is deploying this at scale and I’ve been assembling some best practices. The biggest issues were resolved with v11, and the metadata improvements. One task = 5 channels, so plan repository resources accordingly. If doing a backup copy job, make sure you keep that in mind as well - limit the tasks on the target repo so it doesn’t suck up all the task slots on the source and hang up the RMAN jobs (especially the archived redo log jobs). I recommend increasing the registry settings for max user ports to 64K and shortening the TCP timed wait delay to 30 seconds. Summary of the big points.:Recommendations for infrastructure optimization:Set a backup window for backup copy jobs? No, no need. Reduce tasks on the BCJ target repositories, set to 20 or 30 per extent server BCJ can be set at repo level if there are two Oracle repos with different retention (e.g. for Prod and Non-Prod), or a
You’re welcome. I should have edited item 2, since those numbers related to a ratio of cores on a physical server. It would be better put as “Reduce tasks on the BCJ target repo servers to 10-20% of the tasks allocated to the RMAN plugin tasks.”Hope that helps.
Two more points (this might go on all day...)Dedicate the repository to Oracle RMAN in large environments. Don’t mix in VM workloads. This is both a resource issue and a configuration issue. See the point below. If targeting a SOBR, use the Performance Data Locality policy, so load balancing is based on available compute resources (cores). Note that this means that any Oracle database and redo log backups will likely be spread across extents. This setting works for plug-in backups since there is no Full and Incremental backup from Veeam’s perspective.
Yup, two more points (this is helping me put my list together...):Immutability will not be applied to RMAN backups, if sent to a Linux repository set for immutability. Fast Cloning will not apply to RMAN backup files.
A few more points:Immediate copy is the only choice for Enterprise Application Backups. This has a bearing on managing how the BCJ impacts resource consumption and scheduling. RMAN script: Every backup job process includes the following three phases. Ask customer to separate the catalog resync from the backup/crosscheck steps. The three way connection needed among the database server, Veeam backup server/repo and the RMAN Catalog Database can prolong the duration of the RMAN plug-in backup job. Backup Crosscheck Catalog resync RMAN – dig into the details of how backup jobs are scripted, since this will impact your concurrent task slot usage and duration of each phase. How many backup files per set? How many channels per database backup? How many channels per redo log backup? Does the backup method include Full (level 0) and incrementals (level 1-9), or cumulative incrementals? Full backups daily will consume more repository space, prolong the backup job and prolong the backup co
Correct...and an edit is needed! Use Performance Policy (as opposed to Data Locality Policy), not Performance Data Locality Policy. 🤦♂️
I especially liked the illustrations. They drive home the abstraction of the 3-2-1-1 rule statement (kind of like the Three Laws of Robotics...oh boy, nerd alert). Thanks for this. I’ve shared it and reposted already and have it bookmarked for future conversations.
This is a good and very timely review of basic yet overlooked security best practices. I posted in LinkedIn. Thanks for this, especially after the latest high-profile hack at Colonial Pipeline.
The pointer based synthetic full will be reconstituted as a full backup unless you can clone the file system block for block.Has anyone tried the BackupCopyMirrorAll registry key? This supposedly will work to copy old backup chains from one repo to another.
Thanks for this - it goes into the script immediately.
Great detail, and very helpful. Thank you.
Most of our hardened repository servers are VMs and we use Zabbix for monitoring on those. If there is physical we still use Zabbix but also iLO or iDRAC. What about the risk of a takeover of vCenter, where the bad actor can just delete the datastore containing the repository? Gostev wrote about this in this morning’s Word from Gostev.The monitoring tool suggestion is good thought!
The Backup Service Accounts only apply to the OD and SPO jobs. You can increase threads for the email job, but that doesn’t always allow for increased throughput.Regnor’s suggestion should be tried first.The other thing to do is to strategize backups. Don’t try to back up everything at once. If you don’t want to break the job up into groups, you can go to exclusion and exclude nearly every group. As each group gets the first backup completed, remove another group (or 2 or 3) from the exclusion list and let those complete. Rinse and repeat.Throttling is out of Veeam’s control, but double check your networking to be sure there isn’t anything misconfigured. Then turn off throttling and use exclusions. Finally, please read this document from start to finish. This has EVERYTHING you need.https://www.veeam.com/wp-guide-veeam-backup-microsoft-office-365-v5.html?wpty
it adds the perfect FUD topic for competing platforms to use right at the peak of the mass exodus from on-prem ExchangeWhat are the alternatives to M365? Seems like a monopoly to me (Bad Microsoft from the 90’s)...time for another antitrust suit? This kind of pricing strategy strikes me as supremely arrogant. Or, another way to steer users away from partner solutions like ours. Ugh. 💀
The DBAs should save a copy of their original script before installing the Veeam Plug-in. The thread referenced should answer their questions.
To add my two cents, I have seen a design where the Veeam environment (VBR and repo, VONE, BEM) are in a separate vSphere cluster under a separate vCenter, using a separate shared storage infrastructure (or VSAN). This comes from the same reckoning as the architecture of management clusters for vSphere environments. The same risks about compromise of the VMware components exist, and other complications may ensue if a management domain is used (as recommended by Edwin), but this design has some interesting advantages in terms of deployment and management tools. In my day as a VMware engineer, I was taught (and held to it by my first boss) to only recommended and implement a physical vCenter server, for many of the same reasons put forth in this post and in the Forums. That “caution!” has been washed away by the sands of time, it seems.No one size fits all, but as was stated in the forum thread, backup is all about risk management. You decide!
Well done, Joe. Clear, simple, easy to achieve.
The first two links take you to the same place:Security Readiness Best Practices with Veeam Platform v12
I’m going to bookmark this for new customer conversations. Thanks!
I worked as a storage and backup admin at a North Carolina state agency. We had backups on DAT (often unreadable), Optical Jukebox disk (delaminated often), reel to reel and Super DLT. Some of it was backed up with Arcserve (Cheyenne), NetBackup, Backup Exec, cpio, CommVault, and to JMeixner’s point, copies of documents. Email was backed up with Netscape (can you believe they had a backup solution?). You get the idea. Boxes of various media were stored in the state archives, without a clear plan or documentation of the software used to back it up (and needed to restore) nor the equipment to run that software and do the restore. I call it the “Bell Jar”: put your old backup server and tape/whatever equipment under a bell jar and hope it works in 5 or ten years. Long term management of long term archives is a significant problem and I don’t think there is a workable solution for it, other than the transfer every few years to new media and preservation of the software used to back it up.
Really handy customer-facing reference, and good reminder/checklist for the Veeam engineer/admin!
I’m looking forward to the following:Direct to Object, corollary to Cloud Protection Agents (the Veeam Repo can be very expensive to run in public cloud!) Support for VBAWS v6 and VBAzure v5 for my cloud customers Support for VB365 reporting Improved support for Immutability Reports and Alerts Backup Chain Improvements - so many reasons!
Already have an account? Login
Enter your 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.
