A 4D database can be an integral part of any system or business operations as it can simply be a tool to store data and go above and beyond to work with the data and provide services for users. However, as Murphy’s Law states, “Anything that can go wrong will go wrong.” As such it is always important to have a contingency plan and know what to do in cases of emergencies and accidents. There are a number of issues that can happen and there are a number of ways to handle them to reduce the amount of time the 4D database is down. This Technical Note will be the first of a two-part series. The first part will be a general informative overview that will go over 4D’s features that can be utilized to cut downtime in case a database is damaged. These features are the backup system and how to set up and use a mirror. The following second part will go in-depth about the mirroring process and provide more details suggestions and examples of how to implement a mirror for different scenarios.
Download Complete Tech Note: Tech Note Document