How to Configure SQL Server Backup with MSP360 Managed Backup Service
Backing up Microsoft SQL Server and its databases is crucial for any organization that relies on it, and it is an essential task for MSPs. Due to the large amount of data and frequent changes, this process requires specific measures.
In addition to copying all the data, it is crucial to keep track of all modifications so that everything can be recovered to a specific point in time if necessary. To achieve this, it is highly recommended to combine various types of backup methods, such as regular full backups, frequent differential backups, and transaction log backups. Full backups save all data, differential backups capture changes, and transaction logs record all transactions.
MSP360 Managed Backup Service is a comprehensive solution that allows you to back up your Microsoft SQL Server with all its components, providing full integration with the server’s mechanisms to prevent data loss. With its many features and user-friendly interface, MSP360 Managed Backup Service makes it easy to create a backup of your server. To back up your server using the MSP360 Managed Backup Service console, follow the instructions below.
Setting up SQL Server Backup with MSP360 Managed Backup Service
Setting up SQL Server Backup with MSP360 Managed Backup Service
To access the backup options for a specific server using MSP360 Managed Backup Service, first open your console and navigate to the Remote Management tab. Then, locate the gear icon located next to the desired server and click it to reveal a drop-down menu. From this menu, select the option to Show Plans.
Next, locate and click the plus icon, and then select the option for MS SQL.
Provide a name for your plan.
Specify the backup destination for your data – either local storage, cloud storage, or both local and cloud storage for greater data redundancy in accordance with the 3-2-1 backup rule.
To proceed, select the SQL Server instance that needs to be backed up and specify the type of authentication required. If you choose SQL authentication, you will have to provide your username and password. You can also verify the permissions by selecting the appropriate checkboxes and use a secure connection if necessary.
Select the databases you want to include in the backup. You can choose to back up all databases, specific databases, or exclude certain databases from the backup. This allows you to customize the backup plan to fit your needs.
If you want to use minimum space in the storage, you can enable compression. For additional data protection, you can use encryption, but keep in mind that if you forget the password, you won’t be able to recover your server.
After selecting the databases you want to back up, the next step is to specify the retention policy. The default options are already displayed on the screen but you can customize them to suit your needs.
- There are different options you can choose from such as changing the number of full backups to keep, along with the differential and transaction log backups. You can also delay the purge for more than the default three days to give yourself more time to determine whether you need the backups that are going to be deleted.
- Alternatively, you can choose to delete outdated versions which include full backup, differential backup, and transaction log backups. The retention policy settings allow you to optimize your backup storage and ensure that you have the necessary backups to recover your data in case of any data loss.
Define advanced storage options, if needed.
In the next step, you need to define a schedule for your backup plan. While you can run the plan manually or choose a specific date to launch it, it is recommended that you select a schedule based on your estimated Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
Furthermore, you can specify what the solution should do if the plan runs for too long or if it was missed due to a computer being down. Additionally, the “Alert plan as overdue after” option lets you receive a notification if the backup plan fails after the defined number of days.
The Recurring (advanced) option is suitable for those who prefer to customize everything manually. With this option, you can set up the exact starting time for every component of your backup plan, including full, differential, and transaction log backups. You can specify the exact day and time when each component should be performed, as well as how often they should run. This level of customization allows you to create a backup schedule that perfectly aligns with your organization’s needs and priorities.
The Pre / Post actions section enables you to synchronize your local repository with backup storage before or after the plan runs. You can also set up a script to run before or after backing up your files, or choose another plan to be launched after the current one. This feature allows you to automate additional actions that may be required as part of your backup process.
Finally, you can set up notifications to receive emails about the success, partial failure, or total failure of the backup plan. This way, you can always stay informed about the status of your backups and take action if necessary.
You’ve now learned how to configure a backup plan for your Microsoft SQL Server using the MSP360 Managed Backup Service console. Alternatively, you can use the Managed Backup Server agent, which provides a similar wizard interface, to set up your backup plan on the desired computer.