Database Backup Guide

Manual backup is one of the most important protection steps in QBM, so the file path, permissions, and document options should be reviewed carefully each time.

Administration & Setup Protection End-User Guide

Overview

Tab Path: Configurations > Backup > Backup Database

The backup wizard helps users create a company backup file and review where it will be saved. It also includes options that affect convenience, size, and later recovery.

This guide is based on the actual backup screen, including the automatic file-name option, document-backup option, and schedule-related options.

Main Screens

Screen Tab Path Use It For
Backup Your Company Database Configurations > Backup > Backup Database Create a manual company backup file and review backup details.
Browse File Name Backup Database > Browse Choose the destination file name and folder.
Backup Schedule Backup Database > Schedule Move into the scheduling workflow if that option is available in the environment.

Important Fields And Controls

Field Or Control What It Means
Automatically create a file name and save it in the default backup directory Lets QBM create a suggested file name and store it in the default backup location.
Backup documents Includes attached documents and pictures such as logos and PDFs, which can increase backup size.
File Name / Browse Controls the backup file path and destination. QBM supports QBM backup files and SQL Server backup files.
Schedule a backup Opens the scheduling flow where available.
Schedule a backup using SQL Server agent An environment-dependent option for supported setups.
Company Name / Database Name / File Path The review information shown before or after the backup process.

How It Works

  • The backup workflow prepares a file name, checks permissions, and creates the selected backup file.
  • QBM can suggest a path automatically, often based on the current database name and date.
  • Scheduling options are environment dependent and may be limited outside the main server or in certain editions.

Best Practice

  • Keep at least one recent backup outside the working machine or working folder structure.
  • Include documents when the business needs full recovery of attachments and logos.
  • Test backup usability as part of your wider recovery process, not just file creation.
  • Name backup files clearly so support can identify the right recovery point.