# How to Back Up the JobBOSS Database

> Source: https://netray.co/erp-help/how-to-backup-jobboss-database
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

JobBOSS stores its data in a Microsoft SQL Server database, so a backup is a SQL Server backup, not a copy of program folders. Take a full backup on a schedule, verify it with RESTORE VERIFYONLY, copy it off the server, and take an extra one immediately before any upgrade. Practise a restore into a test database at least once so you know it works.

## Kind

how-to

## System

job-shop-erp

## Erp

JobBOSS / JobBOSS2 (ECI)

## Module

Administration / SQL Server backup

## Query

how to backup jobboss database

## Alternate Queries

- jobboss sql server backup
- restore jobboss database
- jobboss backup before upgrade

## Applies To

JobBOSS and JobBOSS2 on Microsoft SQL Server or SQL Server Express, on premises. Database names, file locations and instance names vary by installation.

## Steps

### Set up a reliable JobBOSS backup

**Items:**

- Find the SQL Server instance and the JobBOSS database name. In SQL Server Management Studio, connect to the instance and expand Databases, or check the connection settings used by the JobBOSS client.
- Check the recovery model: right-click the database, Properties, Options. Simple recovery needs only full (and optional differential) backups. Full recovery needs transaction log backups too, or the log grows without limit.
- Run a manual full backup first (T-SQL below) to a folder on a different disk than the database files.
- Schedule it. On Standard or Enterprise edition use a SQL Server Agent job. SQL Server Express has no Agent, so use Windows Task Scheduler running sqlcmd with a script.
- Verify each backup with RESTORE VERIFYONLY and CHECKSUM, and keep the result in a log.
- Copy backups off the server to a separate location, and keep several generations, not just last night's file.
- Test a restore under a different database name on a test instance, then open JobBOSS against it to confirm the data is usable.

## Sections

### A basic backup and verify script

**Body:**

Replace the bracketed name with your actual JobBOSS database. COMPRESSION is not available in every edition of Express in older versions, so remove it if the statement errors. CHECKSUM makes SQL Server validate pages as it writes.

**Code:**

- BACKUP DATABASE [YourJobBossDb]
TO DISK = N'D:\Backups\JobBoss_full.bak'
WITH INIT, CHECKSUM, STATS = 10;

RESTORE VERIFYONLY
FROM DISK = N'D:\Backups\JobBoss_full.bak'
WITH CHECKSUM;
- REM Task Scheduler on SQL Server Express
sqlcmd -S .\SQLEXPRESS -E -i D:\Scripts\jobboss_backup.sql -o D:\Backups\backup_log.txt

### Pre-upgrade snapshots and restore practice

**Body:**

Before any JobBOSS upgrade, service pack or SQL Server patch, take a fresh full backup and keep it separate from the rotation. An upgrade can change the schema, and the only reliable way back is a restore of the earlier database along with the earlier client version.

To restore, use RESTORE DATABASE with MOVE if you are placing files in different folders, and WITH REPLACE only when you intend to overwrite the live database. Practise with a new database name first so a typing mistake cannot overwrite production.

**Code:**

- RESTORE DATABASE [JobBoss_Test]
FROM DISK = N'D:\Backups\JobBoss_full.bak'
WITH MOVE 'YourLogicalDataName' TO 'D:\Data\JobBoss_Test.mdf',
     MOVE 'YourLogicalLogName' TO 'D:\Data\JobBoss_Test_log.ldf',
     STATS = 10;
- RESTORE FILELISTONLY FROM DISK = N'D:\Backups\JobBoss_full.bak';

### How often and how long to keep them

**Body:**

The right frequency is set by how much re-entry you can tolerate. A job shop that can re-key half a day of time tickets can live with nightly fulls. If you cannot, use full recovery with log backups every 15 to 60 minutes.

Retention should cover the time it takes to notice a problem. Corruption or a bad data load may not be noticed for days, so keep daily backups for a couple of weeks plus monthly copies, sized to your storage and audit needs.

## Pitfalls

- Copying the .mdf and .ldf files while SQL Server is running. That is not a valid backup.
- Storing backups on the same disk as the database, so one failure loses both.
- Full recovery model with no log backups, which fills the disk.
- Never testing a restore until the day you need it.
- Upgrading JobBOSS without a fresh pre-upgrade backup.
- Forgetting that SQL Server Express has a database size limit that backups do not warn about.

## Ai Angle

A read-only assistant cannot and should not take your backups, but it can answer operational questions from the SQL Server metadata, such as when the last full backup of the JobBOSS database finished, how large it is, and which jobs failed. Running on-prem means that question is answered inside your network, without sending server details outside.

## Faq

### Where does JobBOSS store its data?

**Answer:** In a Microsoft SQL Server database on your server. Back up that database with SQL Server tools rather than copying application folders.

### Can I back up JobBOSS on SQL Server Express?

**Answer:** Yes. Express supports BACKUP DATABASE, but has no SQL Server Agent, so schedule a sqlcmd script with Windows Task Scheduler.

### How do I know a backup is good?

**Answer:** Use WITH CHECKSUM, run RESTORE VERIFYONLY, and periodically restore into a test database and open the application against it.

### Do I need a backup before upgrading?

**Answer:** Yes. Take a fresh full backup immediately before the upgrade and keep it outside the normal rotation.

## Search terms

how to backup jobboss database, jobboss sql backup, restore jobboss database, jobboss database backup schedule, sql express backup task scheduler, jobboss upgrade backup, jobboss disaster recovery

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json