2019-10-26, 00:13:14
Hi,
An update. User tc has been able to send me the support bundle.
Forgot to mention it in my reply here, but it is in the main menu -> Help -> Create Support Bundle
After a bit more investigation we managed to track it down that the Vimalin GUI was correct when it said to check the permissions the user that Vimalin was running with could not create the folder structure without elevation.
This can be corrected by making the basic folder structure by hand yourself.
After that Vimalin will work fine as the worker process does not have the same limitations and is responsible for the backups.
So let's write out the steps we took.
Eg. if your external disk is called "Backup Disk" and mounted under "/Volumes/Backup Disk" then first try to create the folder structure by hand -without elevation- to see if you can reproduce the error in the GUI:
Type the following in a terminal (adjust the name of your disk accordingly)
For tc this returned the error: "Permission Denied"..
If you see that then you can continue as follows:
This time you're asked for your password and it should create the folder structure.
You can then go back to Vimalin and add the disk as a backup target in the GUI.
It will think that the disk was used by Vimalin before (it wasn't) because this folder structure is the signature that Vimalin looks for.
After that it will try to look for existing backups, it doesn't matter if you answer yes or no. There are no backups yet, so there's nothing to import into the database.
--
Wil
An update. User tc has been able to send me the support bundle.
Forgot to mention it in my reply here, but it is in the main menu -> Help -> Create Support Bundle
After a bit more investigation we managed to track it down that the Vimalin GUI was correct when it said to check the permissions the user that Vimalin was running with could not create the folder structure without elevation.
This can be corrected by making the basic folder structure by hand yourself.
After that Vimalin will work fine as the worker process does not have the same limitations and is responsible for the backups.
So let's write out the steps we took.
Eg. if your external disk is called "Backup Disk" and mounted under "/Volumes/Backup Disk" then first try to create the folder structure by hand -without elevation- to see if you can reproduce the error in the GUI:
Type the following in a terminal (adjust the name of your disk accordingly)
Code:
mkdir -p "/Volumes/Backup Disk/Vimalin/Archive"For tc this returned the error: "Permission Denied"..
If you see that then you can continue as follows:
Code:
sudo mkdir -p "/Volumes/Backup Disk/Vimalin/Archive"This time you're asked for your password and it should create the folder structure.
You can then go back to Vimalin and add the disk as a backup target in the GUI.
It will think that the disk was used by Vimalin before (it wasn't) because this folder structure is the signature that Vimalin looks for.
After that it will try to look for existing backups, it doesn't matter if you answer yes or no. There are no backups yet, so there's nothing to import into the database.
--
Wil