# AS/400 (IBM i) Backup Verification Checklist

> Source: https://netray.co/tools/as400-ibm-i-backup-verification-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Verify that your IBM i saves actually completed, cover the right objects, are stored safely and can be restored, with critical items flagged.

## Category

erp-operations

## Erp

IBM i / JD Edwards World

## Audience

- IBM i administrator
- System operator
- IT manager
- Auditor

## Tool

**Kind:** checklist

**Groups:**

#### Backup completion

**Items:**

**Text:** Last scheduled save completed with a normal end message, not just submitted

**Critical:** true

**Text:** Backup job log reviewed for objects not saved, locks and authority errors

**Critical:** true

Message queue QSYSOPR and history log (DSPLOG QHST) show no save related errors

Save completed inside its expected window and time trend is stable

Any restricted state save was run when required and ended cleanly

Failures from last week were logged, fixed and re-run

#### Coverage

**Items:**

**Text:** Full system save (SAVSYS and all libraries and directories) exists and is recent enough for your recovery goals

**Critical:** true

**Text:** User libraries saved, including ERP data libraries such as JD Edwards World data and control libraries

**Critical:** true

**Text:** Security data saved (SAVSECDTA) so user profiles and authorities can be recovered

**Critical:** true

Configuration saved (SAVCFG)

Integrated file system directories saved (SAV), including any ERP or integration files

Documents and folders (SAVDLO) saved if used

Journals and journal receivers are included, with a clear rule for changed objects between full saves

Third party product libraries and licence keys documented and saved

#### Media and storage

**Items:**

**Text:** Backup stored on tape, virtual tape or cloud target with its status verified

**Critical:** true

**Text:** A copy is kept off site or in another location, away from the production system

**Critical:** true

Media labelling, rotation and retention are documented

Media inventory shows expired and unreadable tapes are removed

Save files on disk are not the only copy

Encryption of backups is used where policy requires it, and keys are stored safely

#### Restore proof

**Items:**

**Text:** A test restore of at least one critical library was completed in the last 12 months

**Critical:** true

**Text:** A full recovery rehearsal to a spare partition or provider was done within your policy period

**Critical:** true

Restore time was measured and compared with the recovery time objective

Restore of objects with journal receivers and security data was tested

Recovery documents including the order of restore are current and stored off the system

Restored data was checked by the business, for example ledger totals matched

#### Process and governance

**Items:**

**Text:** Backup responsibility has a named owner and a trained deputy

**Critical:** true

Backup software such as BRMS policies are reviewed, and unused ones removed

Change control updates backup scope when libraries or applications are added

Alerts go to a monitored mailbox when a save fails

Backup results are reported to management on a schedule

Recovery point and time objectives are agreed with the business and match the backup design

**Scoring Note:** A backup that has never been restored is an assumption. Treat any unchecked critical item as an open risk with an owner and a due date.

## Content

**Intro:** On IBM i, a backup job that ran is not the same as a backup you can recover from. This checklist walks through completion, coverage, storage and restore proof, so that you can show an auditor or a manager that your saves are real.

**Sections:**

#### How to use the checklist

**Body:** Go through the checklist after a normal save cycle and tick only what you have verified on the system, for example by reading the job log. The critical items are those whose failure usually makes recovery impossible: a missing security data save, a single copy kept on site, or no restore test. Export the finished list to PDF or Excel and keep it as evidence. Run it monthly, and after any change to libraries, hardware, backup software or ERP configuration.

#### What a complete IBM i save includes

**Body:** IBM i separates what you save into several commands. SAVSYS saves the licensed internal code and operating system. SAVSECDTA saves user profiles and authorities. SAVCFG saves configuration objects. SAVLIB saves user libraries, SAV saves integrated file system directories, and SAVDLO saves document library objects. Journals and receivers need a plan for saves between full backups. Many shops use BRMS to coordinate it. Whichever tools you use, compare what is saved with what the ERP and its integrations need.

**Bullets:**

- SAVSYS: system and licensed internal code
- SAVSECDTA and SAVCFG: security and configuration
- SAVLIB and SAV: libraries and IFS directories
- Journal receivers: changes between saves

#### Common mistakes

**Body:** Frequent failures include saving while users hold locks and silently skipping objects, forgetting new libraries that were added after the backup was designed, and keeping only one copy of the latest backup on site. Another common issue is a recovery document stored only on the system that has failed. Finally, many shops measure backup success by the absence of an error message, when the real test is a timed restore with business validation. Schedule that test and treat it as part of the process.

**Cta:** If you want backup and recovery results reported automatically in plain language for your management or auditors, Netray can discuss it. The checklist is complete without contact.

**Faq:**

#### How often should I test an IBM i restore?

**Answer:** At least once a year for critical libraries, and a full recovery rehearsal to a spare partition or provider on a schedule your risk policy supports. Test again after major changes to hardware, backup software or ERP structure.

#### What does SAVSECDTA save?

**Answer:** It saves security information including user profiles, authorization lists and authority holders. Without it, restoring libraries may leave you with objects whose owners and permissions are wrong or missing.

#### Is a full system save needed if I save libraries daily?

**Answer:** Usually yes. Library saves do not restore the operating system and licensed internal code, so a full system save is the base for complete recovery. Frequency depends on your recovery goals and change rate.

#### Can I rely on a replicated copy instead of backups?

**Answer:** Replication helps with availability, but it also replicates deletion and corruption. Most organizations keep point-in-time backups in addition, and test restores from them.

## Search terms

as400 backup checklist, ibm i backup verification, as400 backup best practices, ibm i save restore checklist, savlib verification, ibm i restore test, as400 disaster recovery checklist, iseries backup audit

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