plugout.net

Hello there,

as I intend to backup all my devices to a LAN-only Synology NAS (mainly because it has RAID-1 against unexpected hard drive failure), I want to set fvdw firmware to backup to the Synology NAS using a rsync-only login.

From another OpenMediaVault-powered NAS, I can manually back up to the Synology, though I have yet to work out an automated process.
But fvdw doesn't want to back up to a unique folder that would be dedicated to fvdw:


It always go back to rsync_bckp root folder, but I would like it to go to the fvdw folder.

The weird part is, the fvdw folder created on the Synology does have some content:


I don't understand why there would be both content at fvdw folder created on Synology, and fvdw_date_time folders (created from fvdw firmware) at the same time

How would I streamline its behavior and get everything in the general fvdw folder in the Synology?

The ultimate goal would be to get a full backup of the fvdwsl firmware ready to restore should anything go wrong. The rationale behind this is, as outlined in the help file, there can be only one database backup, and the process of installing fvdw firmware on a blank hard drive is somewhat tedious from what I read, and relies on a Windows-only tool.

How would I backup everything including setttings except the large shares that can be easily replaced?

By the way, I think it would be a bit more user-friendly to have a dedicated "backup" menu item in the left pane.

Hi Cubytus,

What backup mode do you select on your cloudbox? (Miror or incremental)
From what you explains, I believe you selected Incremental backup mode

These datetime stamped folder should content the removed files between two backup

You're right, it's incremental, in case I remove a file that must not be. I would like to have all folders, both the current and past, into the same folder on the other NAS so as to keep everything tidy.

How would I need to configure it for this goal?

Currently , You can't do that.

When you may a incremental backup, you have first a mirror image of you backup folder and in the same level a folder containing the removed files or old file versions. It is the standard behavior of rsync.

But why you did not create first a parent folder on the Synology NAS where you put the incremental backup :scratch

Jocko wrote:But why you did not create first a parent folder on the Synology NAS where you put the incremental backup :scratch

Well this is what I did. The fvdw parent folder I created on the Synology NAS was named as such simply because the fvdw-powered LaCie kept this name on the LAN, but it could be named "LaCie", for example. In other words, fvdw is not named after the fvdw folder I happened to back up first.

To compare with another NAS, OpenMediaVault forces all backups into its own omvbackup folder, created in the rsync target.