Relink not possible for Hyper Backup on Amazon S3 Glacier

[TorbenSchreiter]

Hi there,

the one remaining issue I have after moving all packages to M.2s is with Hyper Backup. I have a regular backup job configured to Amazon S3 (actually Glacier). After the package move it showed up red with a "Relink now" button. Whenever I press it, some process starts, runs for ~15-20 minutes with a progress bar actually step-by-step completing and afterwards the screen looks exactly as before (see screenshot).

EDIT. The Hyper Backup log says:

Error | 2024/10/21 18:08:39 | SYSTEM | [Amazon S3][glhv3-backup-s3-01 - Amazon S3] Failed to run relink task.
Error | 2024/10/21 18:08:39 | SYSTEM | [Amazon S3][glhv3-backup-s3-01 - Amazon S3] Moving backed up files from Amazon S3 to Amazon Glacier is not supported. Please restore files from Amazon Glacier via the AWS Management console.
Information | 2024/10/21 16:57:36 | SYSTEM | [Amazon S3][glhv3-backup-s3-01 - Amazon S3] Relink task started.

Is this an issue related to the the pkg move at all or shall I contact Synology support about it? What would I tell the support team what has happened? Some of the to-be-backed-up shared folders are now on a different volume. Is this the potential cause?

The source volume of the pkg move is, by now, deleted.

Cheers and thanks.

[007revad]

Some of the to-be-backed-up shared folders are now on a different volume. Is this the potential cause?

I would say, yes.

The source volume of the pkg move is, by now, deleted.

This will be a problem. DSM's @database folder would have been deleted.

[TorbenSchreiter]

Try:

sudo ln -s /volume2/@database/pgsql /var/services/pgsql

Then what does the following return?

ls -l /var/services

user123@GLHV3:/volume2$ ls -l /var/services
total 8
drwxr-xr-x  2 http root 4096 Nov 24  2012 blog
lrwxrwxrwx  1 root root   18 Mar  6  2015 download -> /volume1/@download
lrwxrwxrwx  1 root root   14 Oct 25 11:58 homes -> /volume2/homes
lrwxrwxrwx+ 1 root root   14 Oct 19 21:01 music -> /volume1/music
lrwxrwxrwx  1 root root   24 Oct 27 22:48 pgsql -> /volume2/@database/pgsql
lrwxrwxrwx+ 1 root root   14 Oct 20 10:38 photo -> /volume1/photo
lrwxrwxrwx  1 root root   15 Sep 10  2016 printer -> /volume1/@spool
lrwxrwxrwx  1 root root   13 Oct 25 11:58 tmp -> /volume1/@tmp
lrwxrwxrwx+ 1 root root   14 Oct 20 09:33 video -> /volume1/video
drwxrwxrwx  2 root root 4096 Feb  1  2014 Webdav
lrwxrwxrwx  1 root root   21 Sep 26  2021 web_packages -> /volume1/web_packages

(some really old legacy stuff in there)

[TorbenSchreiter]

@007revad Just following up here. I still have @database on both /volume1 and /volume2. What can I do to tell which one of them is currently being used? It should be the one on /volume2 IMHO.

Also, the following symlinks of the above should actually be pointing to NIL. Shall I remove them?

drwxr-xr-x  2 http root 4096 Nov 24  2012 blog
lrwxrwxrwx  1 root root   15 Sep 10  2016 printer -> /volume1/@spool
drwxrwxrwx  2 root root 4096 Feb  1  2014 Webdav
lrwxrwxrwx  1 root root   21 Sep 26  2021 web_packages -> /volume1/web_packages

And these ones should actually be pointing to /volume2, correct:

lrwxrwxrwx  1 root root   18 Mar  6  2015 download -> /volume1/@download
lrwxrwxrwx  1 root root   13 Oct 25 11:58 tmp -> /volume1/@tmp

Thanks a lot.

[007revad]

Did this Synology NAS previously have DSM 6?

/var/services/blog is a folder, not a symlink. At least it is on my old NAS running DSM 6.2.4 (which only contains 2 background jpg files that I haven't seen in maybe a decade).

• blog_bkg_syno.png which is an image of a tropical island
• photo_bkg_syno.png which is an image of hot-air balloons over water

I would just ignore /var/services/blog, /var/services/printer (and /volume1/@spool) and Webdav.

You definitely do NOT want to delete /var/services/web_packages or /volume1/web_packages IDrive and docker (container manager) use web_packages. I'm 99% sure if you delete volume 1 DSM will automatically move web_packages to another volume.

Do you currently have Download Station installed?

In my experience DSM creates a @tmp folder on every volume. Though only the one linked to by /var/services/tmp is used. If you intend deleting volume 1 DSM will automatically edit /var/services/tmp to point to another volume.

[TorbenSchreiter]

Did this Synology NAS previously have DSM 6?

I think the previous DS box that I had migrated from was the one with DSM 6 (a long time ago).

Do you currently have Download Station installed?

I have, but on /volume2 and it is not actually running (and hasn't been in a long time).

In my experience DSM creates a @tmp folder on every volume. Though only the one linked to by /var/services/tmp is used. If you intend deleting volume 1 DSM will automatically edit /var/services/tmp to point to another volume.

Confirming there is a @tmp on both volumes.

What I would like to achieve is disks spinning as little as possible (/volume1 = HDD; /volume2 = SSD). To achieve this, there are three things missing to my understanding:

1. A SATA SSD in a bay with a (non-RAID) /volume3 that is actually only used to allow for a non-HDD to mirror system partition and then use write_mostly. (I am working on that; as per DSM system partition missing on M.2 volume? Synology_HDD_db#367 (comment))
2. Using the original @database that I had moved to /volume2 previously, but that probably is not being used (because of the pkg repair from the v7.2.2 update; as per DSM, version: 7.2.2-72806 Synology_HDD_db#374 (reply in thread)). How do I properly link back to the /volume2/@database?
3. Possibly have the tmp symlink point to /volume2?

[007revad]

write_mostly needs to be set each time the NAS boots. The easiest solution is to schedule Synology_HDD_db to run at boot with the -S option. Not it's a capitol -S (lower case -s is a different option).

If you want to move @download open Download Station then:

1. Click on Settings (the gear icon at the bottom-left).
2. Click on General in the Download Station section.
3. Change "Temporary location" to volume 2 and click OK.

The /var/services/pgsql link should already be pointing to volume2. You can check with:

readlink /var/services/pgsql

To point /var/services/tmp to /volume2/@tmp

sudo rm /var/services/tmp
sudo ln -s /volume2/@tmp /var/services/tmp