HVS32 Backup: general recommendations: Unterschied zwischen den Versionen
Ddang (Diskussion | Beiträge) |
Ddang (Diskussion | Beiträge) |
||
| (3 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
| Zeile 1: | Zeile 1: | ||
| − | [[ | + | [[de:HVS32_Backup:_Grundlegende_Empfehlungen]] |
To resume dispatch in case of failure (hardware defect, data loss due to power outage etc.), we recommend a daily backup of the HVS32 system. | To resume dispatch in case of failure (hardware defect, data loss due to power outage etc.), we recommend a daily backup of the HVS32 system. | ||
| Zeile 9: | Zeile 9: | ||
| | ||
| − | = | + | = General = |
| − | + | Following HVS32 components should be secured | |
| − | *HVS32 | + | *HVS32 installalation path with all sub folders (default C: / D:\Heidler\HVS32 -> most important part is the database under ..\Heidler\HVS32\Database\hvs32.fdb) |
| − | * | + | *All optionally installed components (Datagatewayserver, HVS32-Monitoring, HeidlerLeitcode, Tarifwerk, PVS...). Installation paths by default directly under C: / D:\Heidler\"modulename" |
| | ||
| − | = | + | = References = |
| − | * | + | *During the backup of the HVS installation directory, there should be no active dispatch and the database service Firebird should be closed. Only this way it is ensured that the database is consistent in its backup. All common backup programs support the termination of the services bfore the actual backup and the restart after. Here you have to plan the according downtime for the backup.<br/> |
| − | *Snapshots | + | *Snapshots of virtual machines are not recommended as a backup variant since there is a high risk the HVS32 database contained in the snapshot is defect and can not be used for a necessary restoration. If a backup is created with snapshots or other similar techniques, the corresponding services (Firebird...) should be stopped beforehand.<br/> |
| − | * | + | *Before HVS32 updates, it is recommended (if the Firebird service is terminated) to create a copy of the HVS32 database (...\Heidler\HVS32\Database\hvs32.fdb).<br/> |
| − | *Firebird 2.5 | + | *Firebird 2.5 does provide an option to create incremental backups while the database is in use with the extension [[Incremental_backups_with_Firebird_component_nbackup|nbackup]]. |
Aktuelle Version vom 25. September 2023, 16:11 Uhr
To resume dispatch in case of failure (hardware defect, data loss due to power outage etc.), we recommend a daily backup of the HVS32 system.
HVS32 does not have an integrated backup solution, so the customer/system user is responsible for the backup.
To secure the HVS32, in general you just need a simple file backup of the HVS installation directory as well as existing components (HeidlerLeitcode, Gateway...).
General
Following HVS32 components should be secured
- HVS32 installalation path with all sub folders (default C: / D:\Heidler\HVS32 -> most important part is the database under ..\Heidler\HVS32\Database\hvs32.fdb)
- All optionally installed components (Datagatewayserver, HVS32-Monitoring, HeidlerLeitcode, Tarifwerk, PVS...). Installation paths by default directly under C: / D:\Heidler\"modulename"
References
- During the backup of the HVS installation directory, there should be no active dispatch and the database service Firebird should be closed. Only this way it is ensured that the database is consistent in its backup. All common backup programs support the termination of the services bfore the actual backup and the restart after. Here you have to plan the according downtime for the backup.
- Snapshots of virtual machines are not recommended as a backup variant since there is a high risk the HVS32 database contained in the snapshot is defect and can not be used for a necessary restoration. If a backup is created with snapshots or other similar techniques, the corresponding services (Firebird...) should be stopped beforehand.
- Before HVS32 updates, it is recommended (if the Firebird service is terminated) to create a copy of the HVS32 database (...\Heidler\HVS32\Database\hvs32.fdb).
- Firebird 2.5 does provide an option to create incremental backups while the database is in use with the extension nbackup.