Hi,
after the recreation of a legacy storage pool I try to relink an existing backup.
I backup the data of on QNAP NAS to another with RTRR. I have enabled Client-Side Protection for the backup.
I can restore the data of the backup without relinking the backup. My password works fine there.
When I try to relink the backup it asks for the password, but does no accept the correct password.
Any idea how i could solve this?
(I use QTS 5.2.10.3577 on both NAS)
What is a legacy storage pool?
Only legacy volumes are coming from CAT1 devices, but pools should not exist that way.
You are of course right, it was a legacy volume.
But you cannot create these, you can only have them when moving old disks over from a very old NAS
Whatever the details where, the important point was, that I have deleted and recreated my volume and want to relink my old backup.
As static volume then, it’s not legacy (legacy volumes have severe limitations for size and encryption, so details matter)
I don’t think you can relink the backup as it was a completely different type of storage pool. Probably easiest to just create a new backup job.
My hope was that I could avoid to recreate the backup, there is a lot of data involved and a complete backup takes more then 4 days…
But in the end that is of course always a valid solution.
If it doesn’t work because the storage pool changed, the behavior still seems to be a bug.
I mean the process worked perfect until I had to enter the password.
To tell me that the password is wrong when there is a storage pool problem is extremely missleading!
@dolbyman
I got the legacy term from this message when I had replaced a disk:
The old volume was maybe a legacy volume ?
I do not know how your NAS was/is setup, but legacy volumes come from old CAT1 NAS or OS installs from 2012 and older
I do not remember what the first QTS Version was, but the NAS is not that old. It is a TS-453be from 2019. It had already a storage pool and a thick volume on that.
Regarding the HBS relink issue after entering the password, we have successfully reproduced the problem on our end. We have also asked our internal team to check if there is a workaround available. Thank you for reporting this!
Sounds great, then I wait before I recreate the whole backup from scratch.
