Using Kaseya BUDR Imaging to backup your Kaseya setup? You could have a problem…

Written by BT

I was in the process of setting up BUDR imaging of a Kaseya setup for a client today and realized that using Kaseya BUDR to backup Kaseya, could potentially have a major flaw….

The Problem…

If you’re familiar with Kaseya BUDR, you’ll be aware that by default, Kaseya password protects the each image file it creates. This works great when you’re backing up data for a client, the image is protected by a password and encryption. The potential for disaster is when you’re using password protection in conjunction with the images of your Kaseya server and SQL backend box.

In the event of a disaster you’re going to need to rebuild one of those boxes or both from a BUDR Acronis image. If you’re protecting that image file with a password and your Kaseya system is down, where are you going to get the password from? You’re stuck, the password is stored in the SQL db somewhere and you have no quick and easy access to it

A simple solution…

So a simple solution to the problem is to either:

stick the image password for your Kaseya and SQL servers in your doco somewhere; or the second choice (which is probably better for ease of restore during a crisis)
disable password protection totally for your Kaseya and SQL server images, which you can do from the passwords section on the backup tab. Note that if you reset the password, the next image backup will be a full image backup

To be honest, I’d hope to never have to do a full restore of a key line of business app but in the rare event that you may, this is a useful piece of info to be aware of. Curious to know how you’re backing up your Kaseya system? Are you using the BUDR tools or are you using something else?

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.