v1.5 – Added script to mirror the server.v1.4 – Updated to reflect that the script is now installed by deb automatically.v1.3 – added commented out option for an incremental document backup.v1.3 – altered file name in script to reflect order of operations.Logging to backup script, restoring backup, and tomcat 5.x v1.0 – initial public release on – May 7, 2010.The script can also serve as a basis for a test server where new configurations or versions of OSCAR meet the hard realities of real production data. This can take some time and should be run off hours. The database is also overwritten with a new copy. The documents are rsync-ed across to the new server which yields an efficient and functional backup of the part of OSCAR's data that quickly becomes the largest aspect of the regular backup as only newer files are copied over. This level of complexity may be overkill for a small office, but its not difficult to arrange. Second is the option of having a mirrored server.So we’ll only keep a month of copies on hand at any given time.Īs the files generated are sitting on a network share or the server itself you will still need toĪrrange to have the backups periodically downloaded to removable media (eg disc tape or USB) and taken off site This ensures a complete backup of the "chart" inĪrchive file of the uploaded files will become quite large over time, Dynamically changing files will be backed up including the database andĪll downloaded files. The following describes the backup strategy automatically installed with Oscar12_1 when installed by deb. First, as an essential minimum, is simply a rotating compressed encrypted backup delivered to the network share of your choice accessible through OSCAR Admin.Any production use of OSCAR should be accompanied by a backup strategy
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |