![]() ![]() You don’t need to be a Linux expert to do this. According to the Salesforce backup user guide, you can run a script that will do almost all of the work for you. Veeam Backup for Salesforce diagramĪs for the product installation, there is nothing special about this package. Now, let me use a product diagram to illustrate that architecture in simple icons and arrows.įigure 1. I’m sure VCSPs would appreciate having this ability to deploy a new instance from the code. There is one more thing, in our labs the installation and configuration of Veeam Backup for Salesforce is completely scripted and provisioned via the ansible template. File and metadata storage for each Salesforce organization is isolated, as well as the data storage - each organization would need a separate database to run. ![]() Since we have kept the multi-organization environment in mind, all of the data and file repositories are segregated. But, hey, it’s my huge test environment with 1B+ records to back up. This provides me enough memory to build indexes for larger tables (50+M rows) and enough IOPS for making backups and restores at comfortable speeds. For testing and flexibility reasons, I’m using AWS RDS Aurora (PostgreSQL compatible) with a db.r6g.2xlarge instance (8 CPU, 64 GB RAM). PostgreSQL 12-14 server where the Salesforce data from all objects will be stored.Also, it is a good idea to have the data mounted separately, so you can re-mount this to a new server if needed (upgrade, maintenance). Look at your Used File Space in Salesforce and provision three times bigger volume to retain the data. A data volume for the Salesforce file and metadata backup.Each backup worker consumes additional resources as it runs. Pay attention to the memory here whenever you add more Salesforce instances. For example, for our labs and sandboxes we are using AWS EC2 t3.xlarge instances (4 CPU, 16 GB RAM), but minimal requirements are more modest. Linux server (RHEL 7/8 – compatible) to install a package there.The package can be installed on-premises or in the cloud, and the company will always retain access to the data as there is no SaaS vendor involved in the backup process. That is why Veeam Backup for Salesforce deployment, security and data is fully managed by the customer. How do you know if the data is handled properly? Who has access to this data? This simply does not fit their security model and compliance requirements. We’ve heard from customers that they cannot host their most critical business data in a location, managed by a third party. Unlike other solutions on the Salesforce data protection market, all of them SaaS offerings, we decided to go with a traditional deployment model and here is why: With this new product launch, I’d like to talk more about Veeam Backup for Salesforce’s technical aspects, as well as shed some light on interesting capabilities and architectural decisions we made. While it’s officially a v1 release, I’d like to point out that we’ve been playing with Salesforce data synchronization internally for several years now, until we decided to package our knowledge into a software product. But why backup Salesforce? If you don’t believe you need to back it up, read this first. A few days ago we announced general availability of the new Salesforce solution, Veeam Backup for Salesforce, aiming to help companies eliminate the risk of losing Salesforce data and metadata.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |