Synology SA3200D Active Backup for Business Admin Guide for Windows PCs and Ph - Page 21

Best Practices Relink After creating a replication or backup task, it is important to make sure that you know how to successfully restore or relink your existing Active Backup for Business tasks and backup data, whether they exist on a secondary NAS, in public clouds, or other storage media. This tutorial provides detailed instructions on how to back up and relink your Active Backup for Business data using Snapshot Replication and Hyper Backup. To do this, make sure that your Synology NAS has 64-bit processors, is running DSM 6.1.7 or above, is running Active Backup for Business 2.0.4 or above, and have the necessary packages installed on your Synology NAS. See the Environment section in the tutorial for more details. Mass deployment in Windows environments Active Backup for Business can be safely deployed to all Windows devices in an office. However, when implementing mass deployment, you may encounter the following challenges: • Installation: Making sure that the correct version of Active Backup for Business Agent is installed on all of the source devices. • Setup: Configuring all instances of the agent to back up to the same Synology NAS without making your sensitive account details available publicly. Mass deployment options There are two methods for performing mass deployment when using Active Backup for Business Agent: Customized installer using a dedicated DSM account, and Generic installer using domain accounts. The method you should use depends on if your Synology NAS is integrated with either LDAP or Active Directory Services, which will manage backups. It also depends on whether or not you want to grant end users full privileges for performing restorations. Customized installer using a dedicated DSM account (recommended) We recommend that you set up a separate new DSM user account with limited permissions, exclusively for the group deployment of Active Backup for Business. To set up Active Backup for Business Agent on many computers without supplying login details via email or other means, you can pre-populate the Windows installer (.msi) file for the agent with the login details of a custom DSM account that you have created, or you can supply these details as part of a script. Once you have successfully deployed the agent to all of the devices that you want to protect, you can then change the login details of your custom DSM account to secure your setup. By doing this, you can make sure that no one can use the usernames or passwords visible in the installer file/script to access backups on your NAS. 19