AS/400 IBM i Backup Verification Checklist

0%

0 of 32 items complete

10 critical items still open - these are the highest-risk gaps.

Download checklist:

Backup completion

Last scheduled save completed with a normal end message, not just submittedCRITICALBackup job log reviewed for objects not saved, locks and authority errorsCRITICALMessage queue QSYSOPR and history log (DSPLOG QHST) show no save related errorsSave completed inside its expected window and time trend is stableAny restricted state save was run when required and ended cleanlyFailures from last week were logged, fixed and re-run

Coverage

Full system save (SAVSYS and all libraries and directories) exists and is recent enough for your recovery goalsCRITICALUser libraries saved, including ERP data libraries such as JD Edwards World data and control librariesCRITICALSecurity data saved (SAVSECDTA) so user profiles and authorities can be recoveredCRITICALConfiguration saved (SAVCFG)Integrated file system directories saved (SAV), including any ERP or integration filesDocuments and folders (SAVDLO) saved if usedJournals and journal receivers are included, with a clear rule for changed objects between full savesThird party product libraries and licence keys documented and saved

Media and storage

Backup stored on tape, virtual tape or cloud target with its status verifiedCRITICALA copy is kept off site or in another location, away from the production systemCRITICALMedia labelling, rotation and retention are documentedMedia inventory shows expired and unreadable tapes are removedSave files on disk are not the only copyEncryption of backups is used where policy requires it, and keys are stored safely

Restore proof

A test restore of at least one critical library was completed in the last 12 monthsCRITICALA full recovery rehearsal to a spare partition or provider was done within your policy periodCRITICALRestore time was measured and compared with the recovery time objectiveRestore of objects with journal receivers and security data was testedRecovery documents including the order of restore are current and stored off the systemRestored data was checked by the business, for example ledger totals matched

Process and governance

Backup responsibility has a named owner and a trained deputyCRITICALBackup software such as BRMS policies are reviewed, and unused ones removedChange control updates backup scope when libraries or applications are addedAlerts go to a monitored mailbox when a save failsBackup results are reported to management on a scheduleRecovery point and time objectives are agreed with the business and match the backup design

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.

Optional automated backup reporting

If you would like save results and restore evidence summarized automatically, we can discuss a read-only approach.

Optional. The tool and every export work without this. No spam.

How to use the checklist

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

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.

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

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.

Frequently Asked Questions

How often should I test an IBM i restore?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Operations

More ERP Operations tools

See all

AS/400 (IBM i) Backup Verification Checklist