VCSP Best Practices
Welcome to the VCSP Best Practices guide.
This guide is intended to provide best practices on the different Veeam-powered services for our Cloud & Service Providers. It is not meant as a full documentation or detailed explanation of the features. Please refer to the Veeam Help Center for this kind of documents.
The best practice guide is intended for professionals in search of answers and suggestions to different topics such as:
- start a new Veeam-powered service
- a service (re)design
- scale the service
- pitfalls to avoid
- how to onboard clients to my platform
- different migration scenarios
In general, this information has been developed, collected and updated by the team of Veeam Cloud Solutions Architects working in the field together with Veeam partners.
Be aware that a best practice is not the only available answer. It will fit in the majority of cases, but can also be totally wrong under different circumstances. Make sure you understand the implications of the advised best practices or ask someone who does.
If in doubt, reach out to Veeam professionals in our Veeam forums.
How to use this guide
IF you are an old-time reader of VBR BP Guide, you may have noticed that the layout is similar. The idea for this guide is to resemble the 6 Veeam-powered services, also called use cases, with each having a complete overview that consists of:
- a service description to understand what the service is about
- a high-level design
- the value proposition to the service provider and the customer
- the Veeam solutions required to build the service
- licensing and pricing (brief)
Deep into the use case, we have created sections to design, build and operate the service:
1. Design. You have decided to offer a new service or redesign the existing service already in-place according to best practices. In this section we provide production-ready diagrams/blueprints and how to scale.
2. Build. Once the service has been designed, it is time to build it. An architect can build it themselves, or pass the instructions to other teams to proceed with the deployment. In this section we provide system requirements for the design, registry keys, component deep-dives and general recommendations.
3. Operate. Now that the service is ready and operating, it is time for clients to consume it! In this section we provide topics for day 2 operations such as protecting the service, scaling the database, checking log files, migrating components, updating the service and more.
4. Secure. Generally, everything is designed with security in mind. In this section we provide additional information on topics such as authentication and authorization, security zones and more to come.
We hope you will find the information collected here useful.
Thanks!
The Global VCSP Solutions Architects Team