To design a solution that meets the database requirements for Veeam University Hospital, you need to consider some of the assumptions and implications of using the script for the in-house database. This will help you to ensure the consistency and reliability of the database backups and restores, as well as the compatibility and supportability of the script with Veeam products and features.
According to the Veeam Backup & Replication Best Practice Guide, one of the assumptions that using the script for the in-house database presents is C. The script already exists and is solely managed by the customer.
This assumption means that:
•The script is not provided or maintained by Veeam, but by the customer or a third-party vendor. Therefore, Veeam is not responsible for the functionality or quality of the script, nor for any issues or errors that may arise from using it.
•The script is already tested and verified by the customer or a third-party vendor. Therefore, Veeam does not need to validate or certify the script, nor to provide any documentation or guidance on how to use it.
•The script is already integrated and configured with the in-house database. Therefore, Veeam does not need to modify or customize the script, nor to provide any support or troubleshooting for it.
This assumption has some implications for designing a solution with Veeam products and features, such as:
•The customer or a third-party vendor must ensure that the script is compatible and compliant with the latest versions and updates of Veeam Backup & Replication, as well as with the in-house database.
•The customer or a third-party vendor must provide Veeam with the necessary information and access to run the script before and after the backup or restore operations, such as the script location, parameters, credentials, etc.
•The customer or a third-party vendor must monitor and manage the script performance and results, as well as handle any exceptions or failures that may occur during or after the backup orrestore operations.
