On Demand Backup For On-Premise Munis Clients

Need to take a manual backup of a Munis database

• Munis
• Enterprise ERP
• On Demand Backup
• Year End Close
• Database backup
• SQL
• SSMS

Client needs to take a manual backup of a Munis database in advance of a year-end close or for other 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: Manual backup

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

Option 2: On Demand Backup Job

• This option is only available if you are looking to back up your Production/Live Database
• Please note, this job is set to overwrite the nightly dbexport.bak file. (See Additional Information for more details)

1. Sign onto your Munis Database server as Tylerservice, or equivalent account
2. Open SQL Server Management Studio (SSMS)
3. Connect to the SQL instance where the applicable database is located
4. Expand SQL Server Agent > Jobs
5. Right click on the Tyler Munis On Demand Backup.munprod On Demand Backup
6. Click Start Job at Step... to execute the On-Demand backup

• The On Demand job 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, it will overwrite it
• If you do not want to overwrite this backup, rename the existing dbexport.bak file BEFORE running the On Demand backup job
  • Ex: dbexport_01012024.bak
• Additionally, once your new backup is created under dbexport.bak, if you need to retain this file, rename it and/or copy it off to another location so it is not overwritten during the next nightly backup and maintenance plan run