2.4.3 Notes on performing a full system backup or recovery
-
All JP1/AJS3 services must be stopped for the duration of the backup or recovery process.
-
In a cluster environment, perform backup and recovery of the local disk and the shared disk.
-
Information generated after the backup was taken is lost when the backup is restored. This can include the following information:
-
Maintenance information generated when the system recovers from an error
-
JP1 events
-
Changes made to the configuration definition information
-
-
If a job is scheduled to execute while the JP1/AJS3 services are stopped, the job will execute as soon as the JP1/AJS3 services restart. However, the job will not execute if you cold-start the JP1/AJS3 services.
-
The JP1/AJS3 includes special files. Remember to back up and restore these special files as part of a full system backup.
-
When you perform a backup and recovery to migrate the entire system, you cannot migrate JP1/AJS3 - Manager to a host that has a different host name. You can migrate JP1/AJS3 - Manager only to the same host or to another host that has the same host name. However, you can migrate JP1/AJS3 - Agent to another host that has a different host name.
In either case, you need to ensure the integrity of all file information, including the information registered to the operating system by JP1 programs, when you perform a full system backup. When you perform a full system recovery, you need to recover all of the backup files you created.
Before you use the commands and backup tools provided by the operating system to perform a full system backup and recovery, you need to fully validate the operation in your environment.