Jocko wrote:You have to work on fvdw-sl side.
So you need first to mount a remote share (so for example a share on your lacie nas with one of its user accounts - at least with read privilege) and use the backup menu to sync the share on the fvdw-sl nas
That's all
Back up system activation
I try to summarize what I understood to back up the lacie network v2 system on the target lacie network v1 system with fvdw firmware.
For speed reasons, suggest not to use the rsync system but to use remote share
I explain what is my goal to get a machine mirroring the lacie 2big network v2 system
Can be used in an emergency.
So it is necessary for me to better understand the back up conditions in both directions
Since once repaired, you can go back to the primary system and vice versa.
1) I must absolutely replicate all users by giving the same permissions to the folders
2) I have to do an integral back up of the primary machine on the secondary
3) In time, repeat the operation incrementally or totally at your choice
What I managed to do after changing the initial admin-nas password I was able to access
In full to the functionality of the system this condition as you have explained and necessary for security problems.
At this point I accessed the menu through file sharing, back up where I made the setting of
By choosing add rsync server
Connection settings on the remote rsync server
Where it locates the lacie 2 big network server that I select
I customize user and password which must be read-only
The default port and the 873 I think it is not good in fact I detect on the primary system
These doors
Open TCP Port: 21 ftp
Open TCP Port: 22 ssh
Open TCP Port: 80 http
Open TCP Port: 111 sunrpc
Open TCP Port: 139 netbios-ssn
Open TCP Port: 443 https
Open TCP Port: 445 microsoft-ds
Open TCP Port: 548 afpovertcp
Open TCP Port: 2049 nfsd
Open TCP Port: 3689 daap
Open TCP Port: 4445 upnotifyp
Open TCP Port: 9000 cslistener
Open TCP Port: 20135
Open TCP Port: 39314
Open TCP Port: 53970
Open TCP Port: 59592
Also do I have to enable remote shell connection on fvdw ?
In this case the door 22 matches with what was detected on the primary system
And also which parameter should I use?
Consider that the lacie 2big when using rsync asks for user and password the system is found
But something is wrong
Log of fvdw
2020/05/29 23:02:22 [9917] connect from LACIE-2BIG.local (192.168.1.144)
2020/05/29 23:02:22 [9917] unknown module 'NAS-di-Mario server' tried from LACIE-2BIG.local (192.168.1.144
Instead you advise me to use remote share if I understand where
using a read user that copies the primary system to fvdw using that can be used scheduler in both cases
I apologize if you consider the questions stupid but not knowing the fvdw system I am not very familiar with I am learning to use it
I find it exceptionally complete but its completeness increases its complexity of use for me