Synchronization methods: Overview
Here are the common methods for synchronizing test and existing systems.
- Moving changed objects
- With this method, you periodically save everything on your existing system that has changed since your last synchronization point. You then restore these changed objects to the new system.
- Moving libraries
- With this method, you periodically copy entire libraries from your existing system to your new system. This method works best when your programs are in separate libraries from your database files. You synchronize the libraries that contain database files.
- Moving individual objects
- With this method, you periodically copy specific objects, such as database files, from your existing system to your new system.
- Applying journaled changes
- With this method, you journal objects on your existing system. You move the journal receivers from your existing system to your new system. You apply the journaled changes to the test objects on your new system. This method is sometimes used in conjunction with moving changed objects.
- Refreshing new system
- With this method, you periodically refresh your new system by restoring an entire copy of your existing system.
Table 1 provides a comparison of these synchronization methods. It also shows where you can read more about each method. You can use these methods individually or in combination.
| Method | Complexity | Risk | Time required for synchronization | Frequency used | Where to read more about it |
|---|---|---|---|---|---|
| Moving changed objects | High | Medium to high | Medium | High | Moving changed objects |
| Moving libraries | Low | Low to medium | Medium | Medium to high | Moving entire libraries |
| Moving objects | Medium to high | Low to medium | Low to medium | Medium | Moving individual objects |
| Applying journaled changes | High | High | Medium 1 | Low | Applying journaled changes |
| Refreshing new system | Low | Low | High | Low | Refreshing your new system |
|
|||||