Best Practices for Remote Deployment and Management of Cloud Backup

Write a script Solution providers can create a script that will allow Carbonite to be deployed and installed onto workstations remotely. A typical remote deployment script would dictate which users should get the software, and that it should be automatically installed on their workstations the next time those users log on to the network.

Use Microsoft Active Directory Microsoft Active Directory software authenticates all users in a Windows-based network and enforces security policies. It’s also a great way to remotely deploy and install the Carbonite client to multiple workstations.

Use Remote Monitoring & Management (RMM) software RMM platforms are particularly popular with IT solution providers, and they’re another great way to bulk deploy and install the Carbonite client.

Before deploying, take some time to strategize Carbonite supports multiple backup policies per company. You can establish backup policies based on what is being backed up, such as a workstation or a file server. Or you can establish backup policies based on which people or groups are being protected. Be sure to map out all custom backup policies before deploying Carbonite to a customer’s endpoints. That will save time over applying the Carbonite default, defining custom backup policies, and then manually changing each computer over to the appropriate policy.

Avoid the temptation to simply set it and forget it It’s important to review group backup policies at least every 90 days to ensure that any changes made within the organizations you support are properly captured by Carbonite. For example, if a client switches to QuickBooks from some other type of accounting software, or if the client adds a new file server location, you won’t want to miss that. Regularly review backup policies and make sure Carbonite is backing up the correct files.

Don’t forget about individual employees You can take the above practice a step further by making sure to regularly review the backup policies assigned to individual employees. Why? Because employees may change roles or job functions, and, as a result, they require new backup settings. For example, a marketing professional might need his or her Photoshop and Web design files backed up. But if that person moves over to a finance role, you’d better make sure to capture backups of the user's QuickBooks files.