OrganiZATOR User's Guide

[Home]  [Init]  [Index]

Save & Restore backup


'The real answer is to make backups of everything, very carefully and very often, being in the worst, since the definition computing "the worst" is "only a matter of time"'. Paul Somerson "PC Magazine: DOS Powers Tools."

These options are complementary.

  Save copy makes a copy of the local work area (file zDB1 of the directory where is the executable) at the address provided for it in the corresponding section of the initial settings (Configuration >> Settings >> Initial settings >> Backup directory path).

For the election of the directory to be used for copying, are valid the usual recommendations in these cases: be sure that the capacity of the destination directory is appropriate to the size of the file to copy, and keep in mind that usually is a bad idea to use the same volume of the original directory. The best is to use a different physical drive, or at least a different volume. If you do not have a specific site and has more than one computer, it may be a good idea to make cross copies using a directory ad hoc in each computer to the copy of the other.

Warning:  do not fall into the trap of defining the same backup directory for different dBases, because every copy goes to overwrite the previous one (only retain the last).  If you use several dBases (several work areas) on your installation, use different directories for each [1].  Remember also that must perform a backup of your mailbox, if have established its situation out of the local area [2].

Keep in mind that the copying process only can begins when there is not happen any transaction with the dBase by any user, and while it lasts, nor will it be possible to carry out transactions on it.

Note: as you can see, the system backup scheduled, has a unique site for backup (a copy is better than nothing), but if you have enough storage space, our advice is to establish a structure of three copy levels, or better weekly (a different copy destination for each day of the week). This can be done easily by creating the appropriate copy commands and adding them on the menu of executables (see Command catalog).

  Restore copy performs a process reverse to the previous, copy the file zDB1 of the backup directory in the current (when the executable is located).

The process can not be completed if any user is using the dBase, and this includes you, so that you can not restore the copy if has accessed to the dBase or the Planner areas (no matter that has been closed later, because the connections are maintained). Consequently, in order to restore the copy, it is necessary that any external user is using dBase, and carry out the restoration immediately after starting the application and before access to dBase or the Planner.


[1]  Many years I have gotten into this, and the experience has taught me that in addition to the foregoing, the best measure is to keep at least monthly, a backup of data (say, on DVD) and store them in a site physically other than the original data. Consider for example, that one morning back to the office and found the fire fighters at the scene where should be your office, or that the thief have "cleaned" the office. In my opinion, what happens in computer with the backups is analogous to what happens in electrical engineering to put up a proper land; everyone knows that they are necessary, but usually it is not carried out properly and/or is not checked until a disaster happens.

[2] In any case, if you have established a plain to backup the dBases of all areas (all zDB1 files in your LAN), is sure that you make the backup of all mailboxes.