On Demand Backup For On-Premise Munis Clients

Need to take a manual backup of a Munis database

• Munis
• On Demand Backup
• Year End Close

Client needs to take a manual backup of a Munis database in advance of a year end close or for other various reasons

There are multiple options to take a manual backup of a Munis Database. Keep in mind that backups can take minutes or hours to complete depending on the size of the database and can affect server performance if run during business hours

Option 1:

1. Sign onto your Munis Database server as Tylerservice, or equivalent account
2. Open SQL Server Management Studio (SSMS)
3. Connect to the Server\Instance that your Munis Databases are located
4. Expand Databases> right click on the database you need to back up>Tasks>Back Up...
5. 
6. Back up to Disk. If there is a location already populated, remove it and click Add... to choose the file name and location to save the backup to. Click OK
7. Under the Media Options tab select Overwrite all existing backup sets and Verify backup when finished. Go back to the General tab.
8. Double check that fields are all correct and click OK when you are ready to start the backup. Let the backup run until completion and verify it is backed up to the location you specified.

Option 2:

This option will only apply if you are looking to back up your Production/Live Database

1. Sign onto your Munis Database server as Tylerservice, or equivalent account
2. Open SQL Server Management Studio (SSMS)
3. Connect to the Server\Instance that your Munis Databases are located
4. Expand SQL Server Agent>Jobs
5. Right click on the Tyler Munis On Demand Backup.munprod On Demand Backup> Start Job at Step... to execute the on demand backup. This will automatically create a backup file named dbexport.bak and will save to your default backup location of your nightly backups. If you already have a dbexport.bak file in this location, from the previous night and wish not to overwrite it, you will want to rename the existing dbexport.bak so it is not overwritten. Additionally, once your new backup is created under dbexport.bak, you will want to rename it and/or copy it off to another location so it is not overwritten during the next nightly backup and maintenance plan run.
6.