Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment
Back up and recover the application serving environment
The product uses many operating system and application resources that you should consider adding to your backup and recovery procedures.
WAS resources can be saved while the product environment is active. When backing up database data, you may have to shut down some or all services if a snapshot cannot be obtained. This would occur if there are requests which obtain locks or have open transactions against the database being saved. In a distributed environment, you may need to consider how to get a consistent backup across several systems. If the data on systems is not closely related to data on other systems, you may be able to backup each system in isolation. If you need a snapshot across systems simultaneously, you may need to stop activity on all systems while the snapshot is taken.
How often you back up resources depends largely on when or how often you expect them to change.
Procedure
- Back up your product environment configuration.
This category covers the resources that define your WAS operating environment. Once we have done initial setup, this information should change very infrequently. You might backup this information only when you change these settings, and not include these resources in regularly scheduled backups.
- Administrative configuration files
- HTTP configuration (see the documentation for your web server)
- Back up the applications.
This category covers the applications you run using the product. You should back these up the same way you back up other applications on the system. You could backup these resources every time you add or change an application, or include these resources in a regularly scheduled backup.
- Application deployment configuration files
- Back up the application data.
This category covers the data stores used by your WAS applications. Unless the applications serve only static information, these resources are usually quite dynamic. You should back these up the same way you back up other business data on the system. These resources are suited for inclusion in a regularly scheduled backup.
- Servlet session data
What to do next
If the applications are using other resources or services that are external to the product, remember to include those in your backup plan as well.
Back up and restore administrative configuration files
Export enterprise applications
Restarting an application server in recovery mode
Configure transaction properties for peer recovery
Related
Session recovery support