Hi,
databases like sqlserver are VSS compatible. Whenever a backup tool (like VEAM) start a new backup it sends a freeze to all registered “writers,” such as, Exchange, Outlook, and SQL Server. Then all these 'writers' get the change to flush their data and state to disk.
Afaik HFSQL is not VSS compatible. So how do I get a reliable backup?
The hot-backup option of HFSQL itself is unusable as far as I am concerned. It takes way too long to finish. And it creates a second set of files presenting the actual backup.
Another option is to use a little script and shutdown the database before the backup and start it up afterwards. This is an option during nightly backups in most cases. But I also have clients running a VEAM backup every 2 hours or so.
In the end I want system administrators to be able to do their backup and also to be responsible for that. And also to restore a snapshot whenever necessary, without having to call me about hfsql specific issues.
databases like sqlserver are VSS compatible. Whenever a backup tool (like VEAM) start a new backup it sends a freeze to all registered “writers,” such as, Exchange, Outlook, and SQL Server. Then all these 'writers' get the change to flush their data and state to disk.
Afaik HFSQL is not VSS compatible. So how do I get a reliable backup?
The hot-backup option of HFSQL itself is unusable as far as I am concerned. It takes way too long to finish. And it creates a second set of files presenting the actual backup.
Another option is to use a little script and shutdown the database before the backup and start it up afterwards. This is an option during nightly backups in most cases. But I also have clients running a VEAM backup every 2 hours or so.
In the end I want system administrators to be able to do their backup and also to be responsible for that. And also to restore a snapshot whenever necessary, without having to call me about hfsql specific issues.