Install the app
How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

Hyperbackup Target:Off-line

As an Amazon Associate, we may earn commissions from qualifying purchases. Learn more...

4
1
NAS
DS220+
Operating system
  1. Linux
I use the 3-2-1 backup rule. Two identical DS220+ Synology NASs are involved, one NAS is offsite.
I have been using Hyperback up on local NAS to backup on the remote NAS (one way direction) every morning 4am for a year now with no issues.
A few days ago, it stopped working and hoped the problem would go away but it wasn't it.
When I visit my local Hyperbackup, I see, Target-Offline.

I'll write out a few observations, hopefully someone can help suggest a fix.
  • I am able to QuickConnect to the remote NAS and also use the [remote-server].synology.me to login as administrator.
  • No changes have been made to hyperbackup on my local machine for a long time
  • Strangely, I don't get a response when I ping [remote-server].synology.me but I do get a response when I ping [local-server].synology.me
  • The remote hyperback vault is running with no apparent issues.
  • The synology Firewall on both servers are off
  • The remote-server has port forwarding set up for 6281
 
Hyper Backup Vault still installed on the destination? Versions are up to date?
 
Last edited:
Hyperback is installed on the destination server. I also tried removing it/ reinstalling it. Everything on both machines are up to date.

Router Port Forwarding was setup on the destination router remotely via uPnP. I decided to do it remotely not to inconvenience my brother at the remote location. I plan on visiting to set it up manually. Oh well, perhaps I'll get a cookie out of it too lol.
I got a screenshot showing from my brother showing ports 6281(hyperbackup), 5000 (Http) and 5001(https) are forwarded to the NAS. I believe only hyperbackup is necessary for this purpose.
[automerge]1713739557[/automerge]
Follow up.
I went through and re-created the port forwarding on my remote machine. Afterwhich I was successful at starting the backup process, and I believe I went back in time. It shows in the attached photo that the task was started moments ago but failed in 1969 lol

The logs doesn't say much.. an exception has occurred while backing up data and Failed to run backup task. It stopped about 3 minutes after the backup started.

The date made me think of Epoch time so, I looked it up. A date field must have messed up somewhere.
"Epoch time start date
The epoch time start date refers to the Unix Epoch, which is a widely used date and time representation in computing. It measures time as the number of non-leap seconds that have elapsed since 00:00:00 UTC on 1 January 1970. This date serves as a reference point or “zero time” for many systems and programming languages."
 

Attachments

  • funnylog.webp
    funnylog.webp
    15.6 KB · Views: 54
Let try to backup something is small first, a folder or file to test, to check the backup is OK. After that, we can back to the main backup task.
 
Let try to backup something is small first, a folder or file to test, to check the backup is OK. After that, we can back to the main backup task.
On the destination server I created a new shared folder. On the local server, I created a new Hyperbackup, sharing one folder of small size.
When I used the server url [remoteserver].synology.me I got a popup screen and was not able to continue (Screenshot attached).
When I used the IP address of the same server (non static), it worked fine. I was also able to recover a file with no issue as well.

Note: I am able to logon to the remote DSN using the same [remoteserver].synology.me url.
If I attempt to recover using the [remoteserver].synology.me url, I get the same popup dialog box that is attached
 

Attachments

  • success.webp
    success.webp
    20.3 KB · Views: 40
That date/time being completely off could be a problem as SSL certificates rely on accurate time. For instance, my old MacBook Air had some process that kept it consuming battery while it was supposed to be hibernated, resulting in it needing to be recharged in order to start using it again. The result was some open-on-launch apps that accessed online services would complain until I ensured that date/time was correctly set.
 
I know very little on the subject. The url I use won't work at all in hyperbackup but I can login to the remote nas via the [remote-server].synology.me url.
That being said, if you are not spot on, I'm sure you are close to the issue. I believe it is related somehow.
I had checked in Regional Options in both NASs and both are synchronized to the NTP Server. No changes here since both units were setup initally. The date/time reported in both units are correct when I check.
I very much appreciate your post.
 
Have you tried to power cycle both routers and both NAS?
And checked if the IP address is still the same as before (IP client versus ip in HB task)?
Any blacklisted IP's in the target nas firewall?
 
On the destination server I created a new shared folder. On the local server, I created a new Hyperbackup, sharing one folder of small size.
When I used the server url [remoteserver].synology.me I got a popup screen and was not able to continue (Screenshot attached).
When I used the IP address of the same server (non static), it worked fine. I was also able to recover a file with no issue as well.

Note: I am able to logon to the remote DSN using the same [remoteserver].synology.me url.
If I attempt to recover using the [remoteserver].synology.me url, I get the same popup dialog box that is attached
Please check the logs of remote nas and to see if this nas block the local nas because of many attempts login but successful ?
P/s: Sorry for my late reply because I had to go to the farm for fertilizer.
Good luck!
 

Attachments

  • Screenshot_2024-04-25-10-49-18-214_com.android.chrome.webp
    Screenshot_2024-04-25-10-49-18-214_com.android.chrome.webp
    270.8 KB · Views: 46
I got a screenshot showing from my brother showing ports 6281(hyperbackup), 5000 (Http) and 5001(https) are forwarded to the NAS. I believe only hyperbackup is necessary for this purpose.
Synology made a change, where the first initial HB connection to another remote HB site, needs to have 5001 open for the authentication. Once authentication is made this port can then be closed and the job will run over 6281. I don't this is your issue since the job had been running for some time and now stopped working.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Popular tags from this forum

Similar threads

  • Question Question
Welcome to the forum In a word, no. It should not delete the original files at all. The only thing that...
Replies
1
Views
153
The configuration is part of the main Postgres DB that is running under DSM controlling all of packages...
Replies
5
Views
201
In my case, the integrity check failed due to the default time limit < 30 minutes. Once I set it to 'no...
Replies
1
Views
747
So, interestingly, I tried again from my tablet. The mobile browser doesnt support the "pop-up" login, so...
Replies
20
Views
3,044
For mixed size files, this speed seems ok to me. Many small files bring back read/write speed...
Replies
1
Views
822

Thread Tags

Tags Tags
None

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending content in this forum

Back
Top