2021-09-26, 09:51:54
Hi Kevin,
You've been busy while I was away from the keyboard
Let me try to answer some of your questions.
1) The backup location.
This is a design decision.
The reason for it is that it means that by selecting a disk the program can scan the disk and immediately locate the backups stored on it and offer to import the backups.
2) Automatic zip after backup
Yeah I know, it's on my list of things to do.
It should be easy as the components are all there and have been for a long time.
Just never got to the part to automate that and surprisingly you are the first to remind me of that.
3) Changing storage directory name
Another design decision, not likely to change soon.
I think the proper way to handle your request is to have the option to call a script after the backup finishes.
It's not exactly the first time I've had that idea, but I now made to sure to log it as a feature request.
4) access violation on vimalin.exe when you shutdown your host. I have no idea.. Might not be easy to track down as attaching a debugger on a machine that shuts down would only work on a remote debug session and even then the initiated shut down might succeed.
FWIW.. the vimalin.exe program is only a GUI. After you initiated or scheduled a backup, it can be closed. The worker process is what takes care of the backup, not the vimalin.exe app itself.
5) There's a config file with options
Not that there's a lot you can do there now. You can turn off the file hashing in order to speed up the backup and there's a few hidden options that should make it into published functionality.
See https://forums.vimalin.com/viewtopic.php?id=43 for more details
6) Restore from another directory
I would have to investigate. For now I have logged this.
--
Wil
You've been busy while I was away from the keyboard
Let me try to answer some of your questions.
1) The backup location.
This is a design decision.
The reason for it is that it means that by selecting a disk the program can scan the disk and immediately locate the backups stored on it and offer to import the backups.
2) Automatic zip after backup
Yeah I know, it's on my list of things to do.
It should be easy as the components are all there and have been for a long time.
Just never got to the part to automate that and surprisingly you are the first to remind me of that.
3) Changing storage directory name
Another design decision, not likely to change soon.
I think the proper way to handle your request is to have the option to call a script after the backup finishes.
It's not exactly the first time I've had that idea, but I now made to sure to log it as a feature request.
4) access violation on vimalin.exe when you shutdown your host. I have no idea.. Might not be easy to track down as attaching a debugger on a machine that shuts down would only work on a remote debug session and even then the initiated shut down might succeed.
FWIW.. the vimalin.exe program is only a GUI. After you initiated or scheduled a backup, it can be closed. The worker process is what takes care of the backup, not the vimalin.exe app itself.
5) There's a config file with options
Not that there's a lot you can do there now. You can turn off the file hashing in order to speed up the backup and there's a few hidden options that should make it into published functionality.
See https://forums.vimalin.com/viewtopic.php?id=43 for more details
6) Restore from another directory
I would have to investigate. For now I have logged this.
--
Wil