systemback backup to network

[Wirezfree]

@technomancer
The same as I received, it seems it's down to access permissions it seems on the "target" media/device.

I have retried various mount locations now to mount the NAS share to /mnt/systemback and /media/dave/systemback , same failure.
I have yet to investigate what the difference is between a USB device or a partition vs the NAS mount point in terms of permissions
It's a little frustrating when all other apps can access the shares without issues


I suppose having the sytemback images/file on external media is not an issue really..
If I had a house fire, or a serious flood, the NAS would be toast anyway.
Maybe I need the NAS in the shed at the bottom of the garden, "offsite backup"

[technomancer]

Here is the answer i received from the developer. (seems this is not supported)

Your question #271517 on Systemback changed:
https://answers.launchpad.net/systemback/+question/271517

    Status: Open => Answered

Kendek proposed the following answer:
The Systemback does not save any partitions, and does not using
container files when creating the restore points (incremental backup
method). The Systemback working on a file system level, so the restore
points storage directory should handle the all permissions, without any
restrictions (like the root filesystem). If you are able to mount (under
a selectable local dir) a shared directory which transfers all file
permissions (just like a local dir), then it might work (but I do not
know, this solution is not supported).

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/systemback/+question/271517/+confirm?answer_id=0

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/systemback/+question/271517

You received this question notification because you asked the question.

[Wirezfree]

Quick update:
responses from Kendek, if I understand correctly point to file/directory permissions not being correct on NAS or mount point..?? ...
I need to investigate to see if I can find out what permissions are for USB drive & 2nd disk that work O.K

So this is what I have for access for read/write:

Code: [Select]

//nas1/systemback /media/systemback cifs credentials=/home/dave/.smbcredentials,iocharset=utf8,gid=1000,uid=1000,file_mode=0777,dir_mode=0777 0 0


[Wirezfree]

I finally got my NAS to mount via fstab method, I used this method, to get the NAS Share mounted, and it worked 1st time.
I then used the "bind method" to link it also to a folder in a directory in /home/dave/ so I can easily jump to the folder.

I'm now able to select it in Systemback... /mnt/files/systemback
((I can read/write to and from it, and see the changes on the NAS Gui))

"However", I get an error on creating a re-store point.
Restore Point Creation Failure: "There has been critical changes in the file system during this operation"

I have posted on kendeks launchpad.
I noticed somebody else with same error from a 2 weeks ago.

I will see what response I get to the issue, and report back....

[Wirezfree]

@avj,

Symlinks do not work also, the destination appears to need a specific mount point & type.
I'm going to have another go at mounting via fstab.


I have all my mounts done via /etc/rc.local like this
They work fine for everything except systemback


Subsequent tweaks have allowed me to use just names, like nas1-syn & nas2-wdc instead of ip address

[avj]

Just a thought here, but could you create a simlink to the network drive and select the simlink in systemback?

[technomancer]

@wirezfree- Cool ! Maybe multiple requests will prompt an interest by the maintainer/developer and hopefully a feature. I didn't see a support/donate on the site.
I will check out FreeFileSync too, thanks !

[Wirezfree]

@Jerry, I will add a comment/request on systemback launchpad

@technomancer,
I have used FreeFileSync for quite a while, it's crossplatform, and works with my NAS mounts & Local Shares
Very good for keeping everything in sync, PC's <> NAS and also NAS <> NAS
EDIT: Looks like we added on systemback launchpad at nearly the same time.

[technomancer]

I currently am using SyncBackFree on my windows7 partition. I have a separate partition i share between LinuxLite, windows7 and LinuxMint that is 700Gb(411 used) of just user files. 78 GB on my LinuxLite system I need to transfer. It would be great to have the same features on LinuxLite/SystemBack as well. Anything to not boot into windows. LOL

Here is the link--> http://www.2brightsparks.com/freeware/index.html
FYI: I use the free edition, which for basic backup is perfect, lots of options. Most paid features are for IT professionals.

@Jerry, I am going to see what I can do to support the Systemback project and lobby for the feature.
Here is the question I posted to the developer-->
I am currently running LinuxLite 2.6. SystemBack works for my local drives however I want to backup to my
Debian server SMB shares.
Is this possible ? If so how ?
 I am unable to see my network SMB locations when selecting a destination.
I currently use SyncBackFree on my windows7 partition to backup, but am searching for a Linux solution.

[Jerry]

Backing up to a network location is a useful feature I feel. Lobby the developer for this feature

[firenice03]

I'm testing a backup (restore point) now over network to a NAS... Its FreeNAS running on a VM (Virtual Box).
It mapped via smb in the address bar; I browsed to it by "Browse Network", it mounted the NAS and folders - then set path in Systemback... As far as formatting I think I have that share as ZFS..
I ran with defaults but there's not much on this system (should be a relatively small file)

I'll confirm more after backup completes - running it on my puny system (The Dell Mini in my sig)

Hope the info helps? Maybe the EXT4 formatting??

****UPDATE - NOT TO NAS****
Confirmed, Systemback allowed mapping to /media/"myfolder" which is usually mounted to my NAS, however it was not mounted  my bad.. When I mounted the path to the NAS - Systemback would no longer allow this as a usable directory, went Red and an X..

Sorry for the confusion - I assume the back up directory could be copied after the fact or scripted but would be a nice addition to save directly to a NAS....

[technomancer]

@wirezfree

I have my network SMB shares formatted as EXT4 on the server.
Maybe I need to configure the backup folder to be shared in a different way instead of SMB ?
The max file size is OK if it was only system files I was backing up.
 I was hoping to backup ALL my user files as well, totaling 78GB. Differential type after initial.

I am not familiar with "rc.local", not sure what it even means. I will look into that.

[Wirezfree]

@technomancer

A bit of googling revealed:
1. Storage location must be Linux File system types, NTFS/FAT do not offer right permissions
2. The Location must be in certain locations, like /home /mnt or already mounted via fstab
3. Max file size of 4GB for systemback file creation size.

There maybe other constraints/design parameter.?

I currently mount my NAS devices via rc.local at boot,
that probably(?) accounts for why they not selectable.
I could never get them to auto mount via fstab, maybe need to re-visit this

[technomancer]

Well, you could try changing the Systemback default storage location.  Not at my PC right now, but I believe the default storage location for Systemback is the /home folder.

I am unable to add my network folder, or even select it. I tried adding it manually in the address field and it is not editable.

[Wirezfree]

I have tried various options, it works to external USB Sticks & Drives.
I current have default pointed at a 2nd Hard Drive in my PC mounted as:  /mnt/vault/SysBack

I just quickly opened Systemback, and it is not seeing my mounted NAS drives.

You could ask Kendek the question of creating file on NAS
He is normally very quick to answer.


GL