Veeam Backup for Salesforce 3.1
Recently active
Dear Community,Veeam Backup & Replication 12.3 has been released! today on December 3, 2024Veeam Backup & Replication 12.3 introduces several notable updates that enhance its capabilities for modern data protection. Download: https://lnkd.in/gUKiXEXFRelease Notes: https://lnkd.in/gDxJ9Td3What's New: https://lnkd.in/g8BxdEk8 I’m planning to upgrade to the latest build as well. if anyone on this latest version please feel free to post here experience with us.
chi sta già scaricando?ci sono sia VBR sia EM ovviamente e anche ONE ha una nuova versione.Il primo articoletto che ho trovato è questo https://www.datamanager.it/2024/12/veeam-presenta-nuove-funzionalita-enterprise-con-la-versione-12-3-di-veeam-data-platform/il PDF ufficiale è qui https://www.veeam.com/veeam_backup_12_3_whats_new_wn.pdfdirei che la funzione più importante sia la protezione di EntraID
I am trying to Do the updates on 2 diff company's that I manage, but currently have a Drive space issue on both of them. Need some guidance on how can i transfer the current installation from C drive to another drive and some assistance on how to move the current configuration from the current server to a brand new server thats going to do the backups.I checked some documentations but was not able to find any good material myself.Thank you in advance
Hello, Trying to use Veeam to do ProxMox backups, I was able to add 1 host from the cluster, and deploy a worker to it, but when I go to add the second host, it tells me that its already added, but its not in the list and VMs from the other hosts are not showing up.I tried via IP or DNS name and results are same, it says:“Failed to register cluster. The Proxmox VE node 192.168.1.226 has already been added to the backup infrastructure”but its not there, see below (the 192.168.1.225 is the first host in cluster and there are 2 more .226, .227. What am I doing wrong here ? The documentation said to add each host individually from the cluster: Important If you want to add a Proxmox VE cluster to the backup infrastructure, consider the following: Each node of the cluster must be added to the backup infrastructure separately. The name of the cluster must not be changed in the Proxmox VE administration portal after you add it to the backup infrastructure.
So folks it finally happened. I backed up and restored a Virtual Machine with Kasten! The Kasten 7.5 announcement stated that they had added Suse Virtualization (Harvester) to the support list. Since I had always wanted to try Harvester this seemed like the perfect time to give this a try. Setting up Harvester nested in a Proxmox VM turned out to be simpler than simple. Normally with new Kubernetes endeavors I do my yoga deep breathing stuff before starting as you often run in to rabbit holes of new problems and deep tech that you have to do some quick deep dive learning on. This was not the case with Harvester where everything seemed to follow Veeam’s old Motto: “It Just Works” . Here are the instructions to setup Harverster https://docs.harvesterhci.io/v1.4/install/indexIf you are nesting in Proxmox make sure to select a cpu type of Host.The VM console will look like this when up and ready to go:The Harvester Dashboard is slick and creating a Virtual Machine was relatively simple an
VBR 12.3 had a pretty big payload across our alliance partners. One of those is the NetApp with the ONTAP SnapDiff API. This is a native change file tracking capability built into the ONTAP OS (differencing engine). This will help customers reduce the amount of time it takes for a NAS backup with changes to complete. This improvement was highly requested by our customers. It is easy to enable when you are adding an “Unstructured Data source” in VBR see link and figure 1 below. Once enabled, you will see messages in the job log on incremental backups figure 2. Please spread the word to your ONTAP customers. This is a v1 version of SnapDiiff more features coming (TBD)😀.Adding Enterprise Storage System as NAS Filer Figure 1 Figure 2Note: There are a few restrictions mentioned in the link above listed below.Native changed files tracking (CFT) is not supported for NetApp ONTAP versions from 9.10.1 to 9.10.1P10. Native changed files tracking (CFT) is not supported for NetApp ONTAP FlexGroup
With the release of Veeam Data Platform 12.3 the Nutanix hypervisor is now displayed in the installation splash screen see figure 1 below. In addition some highly requested features have been added to this release see the screenshots below. Figure 1Enabling Nutanix Guest Tools is now an option in the backup job setup screen in the VBN AHV appliance see figure 2. The Nutanix Guest Tools setting will also be available in the VBR console once the job is created in the VBN AHV appliance. It will appear in the “Advanced Settings” Nutanix AHV tab see figure 3 below. Figure 3You will see a new guest processing settings screen on the VBN AHV appliance. It will direct you to set it up in the VBR console for the job see figure 4 below. Figure 4 The application aware processing and guest indexing is now available in “experimental support”. You can still call Veeam support if any issues arise see figure 5. Figure 5Once job changes are made in figure 5. You will see a synchronized job settings on t
When we enable ‘Guest file system indexing and malware detection’, this mean if the VM source infected by malware then VBR will send alert to us and keeping backup running?If i want to test this, can i testing by simply put eicar file into the source VM?
Veeam send the backup files to a remote system.The network connection between the Veeam-server and the remote system has sometimes short network interruptions.The result is that the backup job run failed.Is it possible to increase the allowed network interruption?We use Veeam 12.2
Hi everyoneSome days ago I posted this entry:This is a follow up, or part 2.I hope you like it. Expanding our Object First OOTBI Cluster – adding nodes and VBR space We will add an extra node to the «Single Node Cluster» to become a multi-node one.The steps are straightforward, let’s see them via screenshots with comments:First of all, we need to deploy the OOTBI VSA which will be added to the cluster,follow the guide from the previous entry, ending after the deployment (don’t create the Cluster again).Select the Option Join To ClusterConfigure your NICThe VSA will check for updatesUpdates found, let´s update itupdating…After the update, you will be pushed to the initial menu, go over it again, and the data (NIC config) will remain, just go forward and continueNTP / NTSOK, now, add your OOTBI CLUSTER IP ADDRESS,The one we used/created in the previous entry, and the objectfirst user password we created.BOOM!Node Added to the clusterNow you see the first two options blurry, and the clust
WHAT A WEEK! This week was a whopper of a news week as well as a lot going on in the Veeam Community. @Madi.Cristil and I are in regular circumstances this week for the episode we’ve prepared for you to watch: Special Department Newsvia @SteveF via @SSimpson SPECIAL 12.3 ADDITIONS: See the What’s New Document for 12.3 here and see KB4696. via @HunterLAFR Vanguard Blog Spotlight via @k00laidIT koolaid.info: Deploying NATS.io for VB365 with PodmanJim’s blog shows how to deploy NATS.io for Veeam Backup for Microsoft 365 with PodmanVeeam News This WeekNEWS: See this press release: Veeam, the World's #1 Leader in Data Resilience, Welcomes New Investors with a $15 Billion ValuationAWARD: Veeam Data Platform Named CRN 2024 Product of the Year: Veeam Software Award and HonorsKBs to Note This WeekSuspicious Files List Updated: If your Veeam Backup & Replication server is not connected to the Internet (as it should not be), KB4514 has taken an update for the Suspicious Files List: KB4
SQL Transaction log backup seems to be failing with "Failed to perform internal backup."We just did a big repair of one of our DBs. When I re-enable the backup job (with SQL transaction log backup), it started failing with the following error. Failed to perform internal backup (DBName): Code = 0x80040e31 Code meaning = IDispatch error #3121 Source = Microsoft SQL Server Native Client 11.0 Description = Query timeout expired COM error: Code: 0x80040e31 We can see data being moved as shown in the Report so is the Transaction Log backup really failing or it is just doing catch up with the large change? I’m sure if we run a full backup or possibly change the log backup interval to longer, this will resolve the error. Thanks.
I have Veeam with a requirement to setup a backup policy with the following structure….weekly backup14 days local copy (storeonce)14 days remote copy (storeonce)move to Scality for 6 months1 monthly is kept in scality for 5 yearsI’m looking to create SOBR for local copy and a SOBR for the remote copy which also contains scalityhowever it seems challenging how I meet these retentions for each tier.comments welcome on best options to configure this.thanks
