RK7 backup issues
1. General information
1.1. You are able to use internal of external backup means.
1.2. Internal means are those inside RK7.
1.3. External means are any other software solutions.
1.4. You have to set backup location on another device (PC, network HDD, flash drive) or at least to sepate HDD plugged in the same computer. If you leave backup path by default (to the same RK7 working folder) you have high risk of loosing data in case main HDD was broken down.
1.5. You must execute backup on before upgrade. Copy to archive manually all UCS software folders. Backup external DB as follows from SQL procedures in advance.
2. Internal means
2.1. Cash server
2.1.1. Set up cash server properties [Backup] section parameters.
126.96.36.199. Quantity of copies - maximum of file sets to keep. After quantity reached limit, oldest will be overwritten.
188.8.131.52. Path - you can change location to save files (default - MIDBASE\backup)
184.108.40.206. Shifts - how many "Additional" backups before close common shift to save. "Archive" folder is used.
220.127.116.11. Needed of not - logical propery will disable or enable backup automatic creation.
2.1.2. You have to use backups carefully: do not put back to operation cash server work.udb from backup, which has another current common shift.
2.1.3. If you've lost the current common shift backup and managed to close at least one common shift after the latest good work.udb appeared in backups, you have to create new cash server instead of backup restore (otherwise you will get wrong common shifts and receipts numbering).
2.1.4. It is very important to have backup location always on at least during cash server uptime, otherwise your cash server will be hanging substantially.
2.2. Reference server
2.2.1. Set up 4 parameters in Options -> Parameters -> Installtion -> Reference server -> Files backup.
3. External backup
3.1. We recommend you backup all ucs applications working folders includig databases, settings, modules and other so that you are able to restore full functionality with accumulative data easily.
3.2. You'd better set remote storage as backup location (general good data backup rule) so that even in case of the computer fully destroyed you would save you data.
3.3. Since windows 7 you may use integrated windows backup and restore system.
4.1. Save you current files and folders (make archive or move to other location) before file replacement.
4.2. Restore only latest available backup.
4.2.1. In case of cash server restore, working DB must be of the same common shift.
5. Recreate / reinstall
5.1. When restore is not possible or not allowed due to system organization, you must create new object of the same type with almost the same settings or reinstall the casual application.
5.2. If you've lost files and folders - copy them only from the same version distributive or working application of the same system other branch.
5.3. Check setting files (ini) before starting new object carefully.
5.3.1. It is prohibited to start application with unique attributes of another object.
5.4. Reinstallation procedure is almost the same as installation of new object.
5.4.1. You shouldn't leave broken/previuos working foldes for new object. You have to install new object to new folder without temporary files made by an old application.
5.4.2. You must not start new server with DB of old one. New (recreated) server must have its own unique new database.
5.4.3. You should give unique system name (network name) to new application.
18.104.22.168. Even if you deleted (set 'deleted' status) to the old/broken object, this didn't delete object from reference DB. Nevertheless in those cases RK7 does not provide unique object properties automatic control - you must control that manually.
22.214.171.124. For report purposes, you may give 'Name','Altname' properties to reinstalled object the same as for deleted one.
5.4.4. Configure all dependences for new object in references the same way as it was set to old one, including usage settings.
5.4.5. Configure all child objects to connect/refer to new (recreated) parent object (both in .ini files and reference DB).