I am using urbackup with several clients. However, every night my urbackup server shuts down. I have noticed that prior to server shutdown, the urbackup clients are still not completed (e.g. client 1 say 49%, client 2 say 76%).
The next morning when the urbackup server awakes, it does not pick up where it left off and everything has been lost, so I need to commence the urbackup again.
Is this normal and/or is there a setting that I am missing?
It is not designed for this.
Perhaps look into somehow suspending/sleeping the server instead of shutting it down. Or wait till backups are finished.
Is there a way through settings to forcibly start the backup by a time. For example, say the server wakes at 7am, the client can start the backup at saying 7.15am?
Hi,
Skipping the troubleshooting aspect for a moment, but maybe the question is why the server is shutting down…?
Was the shutdown planned/scheduled/expected, and is there a reason why it doesn’t stay on overnight…?
Perhaps if the server stays on [as almost all the servers I deal with do, dev ones being the exceptions] then the backups would presumably complete, probably overnight…
Other than that, as @uroni has already said, this isn’t a usual scenario and is one that UrBackup isn’t designed for…
Shutdown is mainly for power consumption overnight when server is not in use.
Is there a way to forcibly start urbackup by a time on server wakeup?
You could setup a cron job to run the command line utility urbackupclientctl
It can start a backup.
thanks giles. i am probably not technical enough to do this.
i was hoping if there was a way through settings. For example, I could specify that the backup occurs the 7th of every month. is this feature possible through urbackup settings?
that way i could setup my nas server to not shutdown on the 7th of every month.
this would allow it to complete the backup fully.
No, I don’t know a way to do that with months. You can configure backups to occur on a particular day of the week though. See the FAQ.
The option to perform the backup specifically at a time/day-of-month is probably feasible, using the backup client…the method will depend on whether it’s a Windohs server or a Linux one…
Windows would be best to use a BAT/PS1 that is triggered by Task Scheduler…whereas for Linux, it’s going to be something in Cron, possibly needing a SH script if the selection and/or settings aren’t controlled by the UrBackup server…
From my experience though, it’s better to have the client server on overnight so that the backup is able to complete and it’s available for the start of the day…but, not my server, not my decision…
Urbackup works on intervals and windows rather than backups at fixed points in time.
If you really want your machine to shutdown every night you could try experimenting with the interval and window for backups. E.g. you could just configure incremental backups every 240 hours = 10 days, file backups every 30 days and set the backup window at 1-7/7-10. So incremental backups will be in the morning every 10 days - only changed files go over the network. File backups happen mornings every 30 days and all files go over network.
Thank you for the comments.
Can I also check whilst the server must preferably stay open 24/7, can the client shutdown part way through a backup and continue on the next day?
Or must the client stay open until the backup has completed?
Hi,
Server should really run through the night, and also means that it can run its housekeeping (cleanup) then too…
Client/s can go offline during the backup process, and it will resume once it comes back - there is a “backup timeout” of ten days (IIRC) before the server will can that job’s run…