Recommended backup strategy
Generally speaking, your environment should be backed up on a regularly scheduled basis. This is typically a standard operation, and we will discuss it in more detail towards the end of this section. In addition, occasional one-off backups may be needed. By considering the proposed backup strategy outlined here, you should be protected for the majority of cases and will be able to perform effective recovery, if needed.
The following table is a summary of the actions described in this section, as well as when and what type of backup to perform:
|
Action |
Backup schedule |
Backup type | |
|---|---|---|---|
|
New installation |
After installation |
One-off |
Offline |
|
Upgrading |
Before and/or after upgrading |
One-off |
Offline |
|
Applying patches |
Before and/or after patching |
One-off |
Offline |
|
Configuration changes |
Before and/or after changes |
One-off |
Offline |
|
Architectural changes |
Before and/or after changes |
One-off |
Offline |
|
Code deployment |
Only if needed |
Never |
Offline |
