I would suggest instead to set up a cron (if Linux) or a scheduler (if Windows) to do the full backup at specific time every day.There are multitude of problems with having a staff access to backup options, some of them:If the osTicket system is used by a lot of people and the database is large, when the backup happens, the tables will have lock on them, which means unintended consequences. You can get around the lock, but then you risk of having inconsistent backup.Apache (for Linux) is being run as nobody or apache (or any other user, depends on distro), which means you will need to deal with access to the database, e.g., passwords.Security risk if your system is visible to outside internet.If you want to backup only tickets/organisations/users/settings, you can do that in Linux by specifying which tables to back up, again, you will risk of having inconsistent database :)I don't think it is a bad idea per se, I might be too paranoid here, but it has a lot of obstacles to consider, while proper backup mechanism (backend) just does not have them.