10. Backup and Recovery
The back up of the LANSA objects should be integrated with your regular IBM i system backups. Failure to do this will be very costly, should a system failure occur.
Backing up your LANSA objects is a vital task which should be carried out on a regular basis. If you are already using LANSA for i and you intend on using LANSA for the Web, then you will need to change your backup procedures.
Different LANSA object types need different backup strategies.
In LANSA, there are:
- LANSA Software ObjectsThese are the objects which make up the LANSA software. They include the programs which allow you to build and maintain the Repository, such as the program which allows you to define a field definition or compile a file. Most of these objects are stored in the LANSA system's program library. Some object are stored in the LANSA communications library.
- LANSA Repository Objects
Repository objects fall into these subclasses:
- LANSA Repository Definitions of fields, files, functions and processes. These objects are stored in the LANSA system's Data Library (i.e. your program source).
- LANSA Executable Objects such as I/O modules, functions and processes (i.e. your executable programs created using LANSA).
- Application data files.
If LANSA COMLIB=QGPL, there are also:
- LANSA Software and Repository Objects NOT stored in the LANSA Program Library or the LANSA Data Library
If you are using a dedicated com library that is not QGPL, then you do not have to save QGPL. If you are using QGPL, it is recommended that you convert QGPL to a dedicated LANSA com library. This setup is documented and it is the preferred library for LANSA. If QGPL is still being used as the com library, some LANSA objects are stored in the QGPL library. Which objects you have in the QGPL library will depend on the LANSA products you have installed and the version of the LANSA products you have installed. Some of them are named DC* (e.g. Host Monitor for Visual LANSA), GU*, LC* (for LANSA/Server), LX* (for LANSA SuperServer) and W3* (for LANSA for the Web). Backup the files at the frequency recommended for LANSA Repository Definitions and the other objects at the frequency recommended for LANSA Software Objects.
- LANSA for the Web - Special Backup Considerations
Additional objects need to be considered for backup. Note that the library specified in the Web administration as the working library contains no permanent objects.
- Web Server Software and Configurations
This is software such as ICS. A backup of this software and your configurations needs to be carried out at a similar frequency to the LANSA Software Objects.
- IFS Objects
These are the images that are shipped with LANSA for the Web, plus additional images that you have created for your applications. They should be backed up at the frequency recommended for the LANSA Repository Definitions.
- CGI Script Library
This library should be backed up at the same frequency as the LANSA Software Objects.
- Multi-tier Deployment
If you have implemented a multi-tier deployment of LANSA for the Web, you will have installed on your Web server machine some software objects in an administration library and in QGPL. The original of these objects is included with the LANSA objects on your Data Server machine and can be recovered from there if required. However, the changes you have made to settings and configurations in the administration library and in QGPL need to be backed up so they can be recovered if needed.
For more information about Backing up your files, refer to: