Backup data Scope of Document The Purpose of this document is to provide general guidance to understand about general backup

strategy on AS/400 system .Each system that we support Should have a backup procedure to protect the data from loss or disaster .Each Customer may have a different backup strategy according to their business need. This document provides some guidance when defining a backup strategy. Introduction Save functions are available for saving various types of data like system data, User data, configuration data, security data etc. SAVE function on AS400, Native OS 400 provisioned to protect various data. Command Go SAVE provides all the save functions available on OS400 for protect data. Save Data 1. Files 2. Libraries 3. Documents and folders 4. Programs 5. Other objects 6. Changed objects only 7. Licensed programs 8. Security data 9. Storage 10. Configuration 11. Objects in directories Save System and User Data 20. Define save system and user data defaults 21. Entire system 22. System data only 23. All user data Save Document Library Objects 30. All documents, folders, and mail 31. New and changed documents, new folders, all mail 32. Documents and folders 33. Mail only 34. Calendars

Save Libraries 40. All libraries other than system library 41. All IBM libraries other than system library 42. All user libraries 43. All changed objects in user libraries Save for Different Systems 50. Save in System/36 format

Below are the commands which are used for run various save operation. (Including BRMS commands). Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Save Object SAV APAR Data SAVAPARDTA Object using BRM SAVBRM Configuration SAVCFG Changed Objects SAVCHGOBJ Document Library Object SAVDLO DLO using BRM SAVDLOBRM Folder List using BRM SAVFLRLBRM Library SAVLIB Library using BRM SAVLIBBRM Licensed Program SAVLICPGM Media Info using BRM SAVMEDIBRM Object SAVOBJ Object using BRM SAVOBJBRM Object List using BRM SAVOBJLBRM Restore SAVRST Restore Configuration SAVRSTCFG Restore Changed ObjectsSAVRSTCHG Restore Doc/Lib Object SAVRSTDLO Restore Library SAVRSTLIB Restore Object SAVRSTOBJ Save Files using BRM SAVSAVFBRM Save File Data SAVSAVFDTA Security Data SAVSECDTA Storage SAVSTG Document Library Object SAVDLO DLO using BRM SAVDLOBRM Folder List using BRM SAVFLRLBRM Library SAVLIB Library using BRM SAVLIBBRM Licensed Program SAVLICPGM Media Info using BRM SAVMEDIBRM

Save Object SAVOBJ Save Object using BRM SAVOBJBRM Save Object List using BRM SAVOBJLBRM Save Restore SAVRST Save Restore Configuration SAVRSTCFG SaveRestore Changed Objects SAVRSTCHG Save Restore Doc/Lib Object SAVRSTDLO Save Restore Library SAVRSTLIB Save Restore Object SAVRSTOBJ Save Save Files using BRM SAVSAVFBRM Save Save File Data SAVSAVFDTA Save Security Data SAVSECDTA Save Storage SAVSTG Save System SAVSYS Save System using BRMS SAVSYSBRM Save S/36 File SAVS36F Save S/36 Library member SAVS36LIBM

Backup strategy Backup strategy may differ from business to business, backup strategy plan can be customized on iSeries .There are many backup recovery tools are available on iSeries market. BRMS is one of the famous backup recovery tool where we Can customized own backup, restoration, media, system, retention policies. Native commands for setting a backup and run a backup. GO backup is the command which provides the options for set own backup strategy on the iSeries system. Set up backup 1. Change daily backup options 2. Change weekly backup options 3. Change monthly backup options 10. Change library backup list 11. Change folder backup list 20. Change backup schedule

Run backup 1. Run daily backup 2. Run weekly backup 3. Run monthly backup 10. Back up IBM-supplied libraries 11. Back up the entire system The backup can customize as Daily, Weekly, Monthly and Yearly backup and special backup as per the retention period of the backup media. Data will be protected based on its criticality. Default retention period for various backups Retention period for DAILY BACKUP Generally the daily backup media are kept in OFFSITE for 8 days then the media data will expire and the media is used for next daily backup. Note :The retention period can differ based on business need. Retention period for WEEKLY BACKUP Generally the Weekly backup media are kept in OFFSITE for 35 days .Media data will expire on end of the retention period and the media is used for next weekly backup. Note: The retention period can differ based on business need. Retention period for MONTHLY BACKUP Generally the Weekly backup media are kept in OFFSITE for Six months .Media data will expire on end of the retention period and the media is used for next monthly backup. Note: The retention period can differ based on business need.

Retention period for YEARLY BACKUP Generally the Yearly backup media are kept in OFFSITE for Minimum seven years .Media data will expire on end of the retention period and the media is used for next Yearly backup. Note: The retention period can differ based on business need.

Retention period for SPECIAL BACKUP Generally the special backup media are kept in OFFSITE for life time and Media never expire Note: The retention period can differ based on business need. Full backup of the object or library. During the backup save all the objects with in the library where the library is included on the backup. Incremental backup: Where it is save only the changed objects in the library or we can specify any reference date during the backup.

SAVE functions by using BRMS tool. SAVING LIBRARIES/OBJECTS There are various ways to perform saves using BRMS. You can do STRBKUBRM, SAVLIBBRM, SAVOBJBRM and SAVSAVFBRM.

STRBKUBRM From a command line type: STRBKUBRM (F4) You will be presented with the following screen:

For control group you must put in the name of the control group that you want to back up. Leave schedule time as *IMMED unless you want to schedule it to run at a certain time. Submit to batch you can either put *NO which will run the save interactively or you can put *YES to submit to a job queue. If you specify yes and press enter it will give you further parameters to put in the job queue you want to submit to.

SAVLIBBRM The Save Library using BRM (SAVLIBBRM) command saves a copy of one or more libraries. This command saves the entire library, including the library description, the object descriptions, and the contents of the objects in the library. For job queues, message queues, output queues, and logical files, only the object definitions are saved, not the contents. From a command line type: SAVLIBBRM (F4) You will be presented with the following screen:

For Library specify the library that you want to save. For device specify the tape drive you want to use for the backup. For media policy specify the media policy that you would like to use with this save (ie: if you want the save to be kept for six months then specify media policy SIXMONTH) For control group leave it as *NONE The rest of the parameters are as the usual SAVLIB command and need to be filled in accordingly.

SAVOBJBRM The Save Object using BRM (SAVOBJBRM) command allows you to save individual objects or a group of objects that are in the same library. The system saves the specified objects by writing a copy of each object on tape, or in a save file. The objects are not affected in the system unless the command specifies that the storage should be freed. Restriction: No object being saved can be changed by a job that is running at the time the save operation occurs unless save-while-active is used. From a command line type: SAVOBJBRM (F4) You will be presented with the following screen:

This is very similar to the SAVLIBBRM command, you need to specify the Library name, the object(s) to be saved, the tape device to be used, the media policy, control group *NONE and the rest of the parameters are as normal for a SAVOBJ command.

SAVSAVFBRM The Save Save Files using BRM (SAVSAVFBRM) command saves save files created during BRMS/400 processing to tape. Various parameters allow you to select which save files that you want to copy to tape. For instance, you can select a range of save file creation dates to include in the save files that you want to copy to tape with further qualification of control group and media class. Expired save files that are not waiting to be copied to tape are deleted when the SAVSAVFBRM command processes. Data in a save file created with device *NONE will never be copied by BRMS to tape. It is intended for online access only. From a command line type: SAVSAVFBRM (F4) You will be presented with the following screen:

Save spool file by using BRMS. Spool files are saved by using BRMS. There is no any OS400 native command for save the spool file. Spool file are listed on the backup list by adding the OUTQ name, and the backup lists are mentioned on control group. Spool files are saved as per the control group. Below is the snap shot which display the saved spool file lists.

Summary: Data are important for a business; iSeries provisioned for protect all the data with customized features. Many backup tools are available for customize the backup by data criticality and reduce the complicity of restoration of data.