ramsesdeux Posted December 13, 2020 Share #1 Posted December 13, 2020 HI Guys, There's this issue that for the life of me can't figure out on how to fix. Here's the context: - I never had any issues running Xpenology nor Hyper Backup before. - Needed to migrate all data from Ext4 to BTRFS - So added new hard drives to my server (Dell Poweredge T320 running ESXI6.5) - New hard drives are all pass-through to Xpenology VM - no issues. - The new hard drives are then within a new Storage Pool / Volume 2 in BTRFS - Then using Control Panel I moved all Shared Folder from Volume 1 TO Volume 2 - Once this done, I shut down services and moved packages from Volume 1 TO Volume 2 following this below:https://veducate.co.uk/synology-moving-a-package-between-volumes/ - All went well! - Once done I removed Storage Pool / Volume 1 - Pulled drives from the server - Rebooted Xpenology - Everything is working fine... except Hyper Backup! (Gdrive / Gsuite) I know the issue isn't related to user rights, but in doubts I totally removed and reinstalled Synology Drive. To no avail. For some reason, there is a missing database? Hopefully one of you here, tech saavy gourou, could point me to the right direction? I'm at a total loss and no idea how to fix Hyper Backup, while I already spent two days on this. Something tells me the solution might not be way more complex, but out of my reach. Thank you so much for anybody assistance with this, Cheers See the following screenshots: Quote Link to comment Share on other sites More sharing options...
ramsesdeux Posted December 15, 2020 Author Share #2 Posted December 15, 2020 "Help me Obi Wan Kenobi, you're my only hope" 😭 Quote Link to comment Share on other sites More sharing options...
jensmander Posted December 16, 2020 Share #3 Posted December 16, 2020 Synology stores system entries in a PostGRE SQL db. Maybe this was damaged or corrupted. Did you try to reinstall the HyperBackup package? This will not affect any existing backups. Quote Link to comment Share on other sites More sharing options...
ramsesdeux Posted December 16, 2020 Author Share #4 Posted December 16, 2020 7 hours ago, jensmander said: Synology stores system entries in a PostGRE SQL db. Maybe this was damaged or corrupted. Did you try to reinstall the HyperBackup package? This will not affect any existing backups. Yes, I completely uninstalled and reinstalled HyperBackup package. Sadly it did not solve the issue the the error message is still the same. You can see the DB error in the log (in red). Quote Link to comment Share on other sites More sharing options...
IG-88 Posted December 16, 2020 Share #5 Posted December 16, 2020 On 12/13/2020 at 11:36 AM, ramsesdeux said: For some reason, there is a missing database? i guess the old backup destination has a db of the content? i'd try to remove access to a old destination (share?), uninstall hyper backup and hyper backup vault, clean manually in the volum(s) in @appstore and then install the packages again make sure the old destination is still unavailable (so no db can be read) and then access a new destination to create a backup the only other db i could think of would be in the volume and named"@img_bkp_cache" on my system it corresponds to the latest backu but i never checked that before the db file can't be something thats on the dsm system partition, it has just not enough space to cope with backup data, even if its just a index, so whatever you are looking for is an a data volume or a share Quote Link to comment Share on other sites More sharing options...
ramsesdeux Posted December 18, 2020 Author Share #6 Posted December 18, 2020 (edited) Thank you for your help @IG-88, really appreciated! Quote i'd try to remove access to a old destination (share?) - How could I do this? Quote uninstall hyper backup and hyper backup vault - Tried already by uninstalling hyper backup, and I never used hyper backup vault... But will do it again. Quote clean manually in the volum(s) in @appstore and then install the packages again - Could you be kind enough to tell me exactly which and all files that I should delete? In @appstore there's usually the HyperBackup folder yes.... but maybe something else to delete? Quote the only other db i could think of would be in the volume and named"@img_bkp_cache" - Can this be deleted safely without compromising anything else? Quote the db file can't be something thats on the dsm system partition, it has just not enough space to cope with backup data, even if its just a index, so whatever you are looking for is an a data volume or a share - Ah understood! This is a really helpful tip! Thanks again for your help 😊 Edited December 18, 2020 by ramsesdeux Quote Link to comment Share on other sites More sharing options...
IG-88 Posted December 18, 2020 Share #7 Posted December 18, 2020 18 hours ago, ramsesdeux said: - How could I do this? remove access rights or rename the share if its a database on the destination is a problem hyperbackup should not be able to read it that way afair the destination is saved inside of a job, so a new job into a new empty destination/sahre should not have that problem 18 hours ago, ramsesdeux said: In @appstore there's usually the HyperBackup folder yes.... but maybe something else to delete? no only the hyperbackup folder in @appstore 18 hours ago, ramsesdeux said: - Can this be deleted safely without compromising anything else? i dont know enough about dsm to be sure, but when searching for it you find things that are hyper backup related so it seems to be safe to delete when hyper backup is removed Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.