Veeam Backup for Salesforce 3.1
News, guidelines and various community projects
Recently active
Hi,since Veeam is offering more cloud features, it would be great to get an new training with a focus on all the cloud features. AWS, AZURE etc. DR/AWSSo as add on to the VMCE Veeam Cloud Certified Engineer :-)
Hi Everyone, I wanted to start sharing some of the content and learning paths I have been taking to get a better grasp on Kubernetes and Cloud Native technologies. First of all I am going to be putting my learning and findings on this page as I continue to navigate these new technologies. And then I will keep adding if possible to this post with the latest blog posts. Part 1 - Choosing your platform Part 2 - Setting up your Kubernetes cluster Part 3 - Playing with stateless workloadsPart 4 - Setting up dynamic shared storagePart 5 - Helm & MinIOPart 6 - Context is ImportantPart 7 - Load Balancing your Kubernetes Home Lab with MetalLBPart 8 – Deploying KubeApps the visual marketplace for all your Kubernetes AppsPart 9 – A Mission Critial App - PacmanPart 10 – Backups in a Kubernetes worldI would love to get your feedback useful links to add or things we should share with the community.
See here how it works in a step by step guide.To start in Instant SQL Recovery wizard, select your server and choose Restore application items.Here you choose if you want to restore to the latest available restore point, or select a listed one. At the end of wizard press Browse. Veeam Explorer for Microsoft SQL Server starts.Choose the database you want instantly recovered and select to do so. You have these options to choose from: Latest restore point. Point-in-time state. Recover to another server. This you can used to recover DB using a different name while original DB is still in place. In this demo, I selected point-in-time state to show additional options.Select point-in-time state you want recover to.Notice:First option recovers to date and time, recovery point was created. Second option lets you choose the exact date and time to restore to. As noted, transaction log backup is required here. Checking option to restore to a specific transaction, lets you choose a marked tran
Why do you think Veeam is in this place today?
With the recent topic of how to change the IP/DNS Name of the vCenter recently posted I wanted to share for those with experience in SQL how you can modify the vCloud URL within Veeam.This requires some SQL knowledge and that you shut down the Veeam services during the process. The main query is as follows:SELECT * FROM Hosts WHERE type=1 OR type=6 OR type=14; Under the "options" column for the relevant row(s) we're going to see the reference(s) to the old cell hostname. Then once you are ready follow these steps:0) Veeam Configuration Backup1) Stop Veeam Services2) Backup VeeamBackup SQL DB3) SELECT * FROM Hosts WHERE type=1 OR type=6 OR type=14;4) Copy the "options" value5) Modify the copied "options" column value to have the new VCD URL6) Note the id column of the related row7) Perform the update query on the objects that need the new URL:UPDATE Hosts SET options='NEW_options_VALUE' WHERE id='ID_FROM_STEP_6';8) Start Services9) Open Console, and "next" through the properties of the
From Veeam Backup & Replication restore Mac OS FileOpen Veeam Backup & Replication console and click Backups, Disk. You will see the Mac Agent Backup. Right-click “Your Mac Device Name”, Restore guest Files, Linux, and other…Select the available restore point.A new feature of v11 is the ability to leverage an existing managed Linux server to act as the file-level recovery appliance, you can choose a Linux host that I have in my environment.v11 will open the Veeam Backup Browser, which enables the ability to see the structure and the ability to recover your files and folders.You can restore folder or file to the v11 Desktop only, If you need direct restore the Mac device, please continue to see “Step by step of Veeam Agent for Mac 1.0 @ Part 3 (Restore from MacOS)” Coming Soon…Reference Link: https://vexperthk.com/2021/03/09/step-by-step-of-veeam-agent-for-mac-1-0-part-2-restore-from-vbr-v11/
Hey everyone!In this episode, I and @Rick Vanover recap this week's activities with a twist RICKATRON was in charge and chose highlights of the week on his own! (he broke the rule again! )Check it out now
i had some discussion on the matter of retention times in context of protection against ransomware/insider attacks. Setting up a hardened repository and making data immutable for a certain amount of time is great stuff to implement. But how long is long enough?I can remember some research or reports stating there is an "average" discovery time of ransomware / encrypted data , but i cant seem to find the articles anymore.What would people here recommend for setting retention times for specifically protecting against these attacks?I'm thinking about something arround 14 - 31 days of immutable daily backups at minimum. Any shorter has higher chance of matching an attackers' maximum amount of patience for example, to just let data expire on the repo before taking action perhaps.Or are you seeing pretty short detection times in your experience and the most recent backup was used most of the time to recover? I'm crossposting from the R&D forum. Perhaps it is better to dicuss this here.
NEW study guide Are you looking to earn your VCP‑DCV 2020 certification ? Well, Shane Williford and Paul Wilk, along with Veeam, have you covered! Grab the latest edition (vSphere 6.7) of our VCP Study Guide.This 131‑page study guide covers all 7 of the exam blueprint sections to help you prepare for the VCP‑DCV 2020 exam. Guide available in .pdf and .epub formats.https://go.veeam.com/vcp-dcv-2020-exam-guide.html
Hi,We are having some backups copied to an AWS bucket using Veeam Backup and Replication 11. The backups have been copying up to the bucket okay but today I was going to practice restorations and am a little confused about whether I did a restore from the internet or from the performance tier. The log said the restore was from AWS Veeam Object1 which should be the Amazon server. It seemed kind of quick. I was expecting it to take hours for a small server. It was 34 minutes. Maybe de-duplication is really good.This was in the log:Restoring Hard disk 1 (40 GB) : 30.3 GB restored at 18 MB/s [nbd] 3.9 GB downloaded from capacity tier, 9.9 GB copied from performance tierSo far I haven’t seen any documentation that specifically walks us through restoration from a bucket.It’s possible I’m still thinking of our network speed with a 2015 frame of mind. I want to be sure I’m doing this right. Thanks,Bob
Visit the Kasten website an complete the lab to get a free KubeCon Europe Passhttps://play.instruqt.com/kasten/tracks/kasten-kubernetes-labEven without the free pass is the lab a great starting point for your journey into containers, Kubernetes and Kasten...
I am using Veeam Backup & Replication 9.5 Update 4.My backups are sent to Amazon S3 buckets after 30 days.I am trying to do a Instant VM recovery from a Restore Point located in the S3 bucket.I ran the restore and the Log file is telling me.Restore session Status: In progress.Log (Last 2 lines)<machine name> has been recovered successfullyWaiting for user to start migrationI don’t know where to go from here. I am having a hard time finding any documentation for this.Using vSphere Client version 6.7.0.46000Any help would be appreciated.
Hello everyone, today I bring you one more step on how to correctly secure our instance of Veeam Backup for AWS v2.To do this we will rely on Let’s Encrypt, the famous open-source project that allows us to generate free SSL certificates.NOTE: This process is not officially supported by Veeam, and any consequence of following the steps incorrectly, or any incidence derived from these steps will leave us without support. We will have to deploy the appliance again, keep that in mind!Where shall I run this Script?My recommendation will be to run it from a Linux VM, Container, or similar that you have already on your on-prem, or in the Cloud. As a last alternative, not supported of course, is to follow these steps inside the Veeam Backup for AWS appliance itself.Installation of system requirementsTo make it all work we’re going to need a couple of packages to do all this automatically:jq The necessary Let’s Encrypt packagesTo install jq, we will launch the following command:sudo apt-get ins
Hey everyone,I wanted to share this recent blog post I made with yourselves as whilst it’s not directly related to Veeam, I was helping someone that had locked themselves out of a Veeam database and needed to take a native backup for a support case with Veeam. I was recently helping a customer create a SQL database backup for a support ticket and noticed that they had an interesting SQL Server configuration. There was only a single account with sysadmin rights, the sa account, but this account wasn’t allowed to sign in. The SQL Server was domain joined but there was just a single group allowed with Windows Authentication and that had the “public” server role only.There are a few reasons this could happen, accidental permission changes, or groups and/or user accounts being deleted from the domain that had been assigned the sysadmin role as examples. Thankfully it’s not the end of the world for you if you find yourself in this situation. Breaking Back into your database! This will invol
Hello There, I just wanted to share an issue I had on one of my customer to avoid others the problem:We setup a standard Veeam Backup & replication Server on a W2019 VM and a Std SQL 2019 on another one to host the DBs from VBR and Enterprise Manager.The DBA from the customer insisted to setup an alias for the DB server when pointing Veeam to its Database server as it’s their best practice to facilitate migration (He was obviously not aware how easy it is to move Veeam Database). So he setup a CNAME that pointed to the real SQL server.The setup went well using the CNAME. We created a “management job” to save Veeam by itself, VBR+SQL servers. The job detected the roles and proceeded as normal but failed on SQL VSS processing. We spent a lot of time to validate that permissions were right (the DBA didn't gave us the sysadmin rights on the backup service account, wise guy) and that the service account on the SQL had the proper permissions too for the VSS writers. Long Story short: I f
