We are excited to announce the release of Kasten K10 version 6.0, the latest and most advanced version of our industry-leading platform that provides enterprise-grade Kubernetes data protection and application mobility. This release helps customers scale their cloud native data protection efficiently. Kubernetes deployments are growing at an unprecedented rate. Gartner predicts that by 2027, more than 90% of global organizations will be running containerized applications in production. However, today’s market conditions are scarred with financial uncertainty and a shortage of cloud native skills. Therefore, you must ensure operational efficiencies are in place to unleash the full potential of your cloud native environments while protecting your data. Additionally, security remains an imperative as organizations focus on keeping their businesses running. With this release, we also continue to innovate in this growing ecosystem, so that you can take advantage of the best-of-breed inn...
Get link
Facebook
X
Pinterest
Email
Other Apps
Who should back up Salesforce?
Get link
Facebook
X
Pinterest
Email
Other Apps
In parallel with Veeam releasing Veeam Backupfor Salesforce, they also published the data protection industry’s first independent research project on protecting Salesforce data by surveying 800 unbiased respondents across three personas (e.g., Salesforce administrators, backup administrators and IT operations) in the 2022 Salesforce Protection Trends Report.
Last week, we looked at “why” (i.e., drivers) organizations are backing up Salesforce, and saw at least nine motivators or concerns behind why organizations back up Salesforce. This week, we’re looking at which personas are involved in defining the strategies and requirements for protecting Salesforce data, as well as who is typically tasked with the backups themselves.
One of the biggest issues organizations tend to deal with when their data is missing and needs to be retrieved is who exactly is responsible for creating a data protection strategy, and what their Salesforce requirements are within the organization.
It could be IT, the Salesforce administrator or the Salesforce consultant. Trying to backtrack and figure out who should have a backup plan in place usually happens after a data loss scenario with no chance of recovery. Salesforce data retention is also often not top-of-mind, since most organizations claim to retain their Salesforce data for less than a year. This short period of time often does not fulfill retention mandates, and losing large amounts of contacts could be devastating to a sales team. With so many people touching Salesforce, it can be hard to know what changes are being made, and how long it would take to discover those changes. With less than half of organizations feeling that they could restore data and metadata within 24 hours. Where would that leave your team with no access to their data?
Veeam Backup for Salesforce eliminates the risk of losing your data due to human error, integration issues or other Salesforce data losses. With incremental sync and flexible scheduling, you can back up your Salesforce data almost continuously. Set your backup to hourly and remove the fear of data loss!
We covered some aspects of the research on our LiveStream on Nov. 1, and we’ll continue looking deeper within a three-part blog series:
For those of us who have been in the business of backing up data for a while, we’re used to making copies of data on different types of media. I won’t date myself by mentioning reel-to-reel tapes, but the journey started with tape and then backing up data to block/file-based disk storage came along. More recently, a new kid on the block has become a popular destination for backed up data, object storage. Veeam started to use object storage as a target when we released Veeam Backup & Replication 9.5 Update 4 in January 2019 by introducing our use of AWS S3 compliant object storage via the Capacity Tier. A year later, we launched Veeam Backup & Replication v10 which featured support for object locking to provide data immutability for object storage. Immutability provides protection from ransomware attacks by locking the objects which prevents them from being modified or deleted by malicious software or humans. Today, Veeam Backup & Replication is protecting hundreds of petab...
Before Veeam Backup & Replication v11, the product used SQL Server to create and store its configuration database. It has always been possible to use SQL Server Express to store a Veeam Backup & Replication, however, this version of SQL Server had some critical limitations. In the 2022 version of SQL Server Express, the most relevant limitations were: Use of one socket or four cores Use of only 1.4GB per instance 10GB limit for databases In an environment of 500 machines or fewer, these limitations may not have an impact, but if you have a large backup environment, you had to migrate to one of the paid SQL Server versions to avoid these limitations. You can check the limits for each version of SQL Server 2022 by clicking this link . For V12 and with scalability, performance and licensing cost in mind, Veeam introduced the possibility of using PostgreSQL as a configuration database. PostgreSQL is a relational database management system that’s been used for over 35 years...
update notice: The information in this blog post has been updated on April 1st, 2022. Since Veeam Backup & Replication version 10, it’s possible to back up NAS shares with the SMB (CIFS) and NFS protocol. One of the challenges with backing up large file shares is doing so in a consistent state. This blog post shows how to create a consistent backup of an SMB share hosted on a NetApp ONTAP based storage. NetApp storage snapshot, Microsoft VSS snapshot or Storage Integration? Veeam offers three ways to back up a NetApp ONTAP SMB share in a consistent state. With NetApp storage integration From a NetApp storage snapshot (without integration) With Microsoft remote VSS snapshot Using the storage integration is the easiest way to get the latest state with very few configuration steps. Using an alternative snapshot path allows complex scenarios like backing up from a SnapMirror/SnapVault location but it involves scripting or a schedule on NetApp to create and delete t...
Comments
Post a Comment