BRMS backup failed when backing up QUSRSYS

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Data backup, storage and retrieval on iSeries Authority restrictions on the AUTL on backup/test systems and AUTL on live system Perform a full system backup without user profile QSECOFR Faster backup method for System i Solve problems concerning the ALLOW OBJECT DIFFERENCES parameter when restoring a library System i backup not advised using network NETBACKUP How to clear expired BRMS created *SAVF files from System i Restore a full system backup from the production partition to the test partition Tivoli Service Manager 6 released with DB2 integration and dedupe Remove a media with a *PERM expiration date from the inventory Booting iSeries from internal or external sources Data backup, storage and retrieval on iSeries Research iSeries Backup and Recovery Authority restrictions on the AUTL on backup/test systems and AUTL on live system Perform a full system backup without user profile QSECOFR Faster backup method for System i Solve problems concerning the ALLOW OBJECT DIFFERENCES parameter when restoring a library System i backup not advised using network NETBACKUP How to clear expired BRMS created *SAVF files from System i Restore a full system backup from the production partition to the test partition Remove a media with a *PERM expiration date from the inventory Booting iSeries from internal or external sources SAVF by FTP on AS/400 -- error "source file not found"

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

You most likely didn't completely "quiesce" your system prior to running the backup of library QUSRSYS and so there were still locks on objects in that library.

Quiesce is a French word. In the context of an iSeries backup, it means, "to bring the system to a quite state". One in which there is very little activity occurring on the system. This is not the same as a "restrictive state", which as you know, is required for a SAVSYS process.

There is a very important difference between quiesced and restrictive states. If you don't take the system down to a restrictive state, you can still run a backup process as an unattended batch job. (Note: In V5R3 BRMS allows you to submit a batch job to the controlling subsystem even in a restrictive state.)

Prior to starting my unattended SWA backup process, I end the following subsystems:

QINTER, QSPL, QHTTPSVR, QSNADS, QSVCDRCTR, QSERVER and QUSRWRK.

I also end the Mail Server Framework via the ENDMSF command.

I'm now in a "quiesced state".... Note, my backup process is still running in the QBATCH subsystem.

In my opinion, it is very important that you have journaling active for any backup/recovery process, too. If you don't, you can never recover any changes made between backups. However, it isn't a requirement of SWA if you "quiesce" the system prior to starting the backup. Once a synchronization point has been established by the SWA process, you can resume normal system operations. If you had to use these backup tapes to recover from a disaster though, you would only be able to recover to the time of the SWA synchronization. If you had journaling active you would be able to recover to the point of your last journal receiver backup.

==================================
MORE INFORMATION ON THIS TOPIC
==================================

Visit the ITKnowledge Exchange and get answers to your backup & recovery questions fast.

Search400.com's targeted search engine: Get relevant information on backup & recovery.

Check out this Search400.com Featured Topic on 30 backup/recovery tips in 30 minutes .