problem with backup sync zyxel from nas542 to nas 326

taceto32
taceto32 Posts: 8  Freshman Member
edited December 2019 in Personal Cloud Storage
Hi i have upgraded nas to 542 from 326 and i have done backup with service zyxelsync from 326 to 542 without problems.Now i use 542 as primary nas and want to sync it with 326 but i have problem becouse 542 return an error starting client server protocol, and i can use only rsync that work but give me void destination even if process says ok.


#NAS_Dec_2019
«1

All Replies

  • taceto32
    taceto32 Posts: 8  Freshman Member
    my idea is to use 326 as backup with zyxel sync and 542 as primary nas.
  • eozrocwd
    eozrocwd Posts: 58  Ally Member
    edited December 2019
    i have problem becouse 542 return an error starting client server protocol.
    What kind of error? Can you explain more information? Has any screenshot?

    Do you want to backup NAS542 to NAS326? Which Type of Backup Planner you used?

    I just test to backup files from NAS326 to NAS540 via rsync and it worked properly.

    If you still have the problem, maybe you can share the setting for checking.
  • taceto32
    taceto32 Posts: 8  Freshman Member
    hi, i have only message in backup planner and in a registry, i use zyxel sync utility and it gives me error, if i use rsync it works but i have blank target even if space is used...how can i view data in target of rsync?i have read that rsync and zyxel sync are the same but zyxel sync make destination same as origin, rsync gives me blank target...






  • taceto32
    taceto32 Posts: 8  Freshman Member
    i have created same folders and users and permissions, and have rebooted 326 and 542 but nothing change,  i have done exact inverse procedure from 326 to 542 with zyxel sync utility without problem
  • eozrocwd
    eozrocwd Posts: 58  Ally Member
    Can you explain more clear about your problem?

    Do you mean NAS326 -> NAS542 successfully, but NAS542 -> NAS326 failure?
    Do you use Synchronization: Mirror or Rsync for backup?

    After finished backup with     Synchronization or Rsync, you should able to see files on destination folder which copy from source folder. And I checked NAS326 -> NAS540 or NAS540 -> NAS326, both worked properly.

    Before you do backup job, do you able to access NAS326 (192.168.2.9)?

    And is possible to share the log information on system?
    You can use telnet/SSH log into your NAS device (source) and username is "root".
    cd /i-data/sysvol/.system
    Here are two log files.
    cat zysync.log
    cat zysyncd.log
  • taceto32
    taceto32 Posts: 8  Freshman Member
    Yes i  mean NAS326 -> NAS542 successfully, but NAS542 -> NAS326 failure
    i use mirror and gives me error, Rsync works but i see no files in destination even if space is allocated and used.I can access in 326 and 542.

    I use custom https port and http and i cannot log in by SSH.Can you give me default port?port 22 is not accessible by user root..and whic password i have to use?

    i leave my configuration for 2 nas

    NasBackup  326
    http port 8900
    https port 449
    user:admin
    pass:Sm@rt3rc0m!

    NasSmartercom 542
    http port  8700
    https  447
    user:admin
    pass:Sm@rt3rc0m!
  • eozrocwd
    eozrocwd Posts: 58  Ally Member
    edited December 2019


    SSH port is 22.


    Can you also share the screenshots of the setting details about Backup Planner?
    And source and destination folder information.
  • taceto32
    taceto32 Posts: 8  Freshman Member
    here is log extracted from zysync.log




    2019/12/11 10:33:25 [1902] @ERROR: auth failed on module Volume1
    @ERROR: auth failed on module Volume1
    2019/12/11 10:33:25 [1902] rsync error: error starting client-server protocol (code 5) at main.c(1561) [sender=3.0.0]
    rsync error: error starting client-server protocol (code 5) at main.c(1561) [sender=3.0.0]
    2019/12/11 10:34:23 [2173] @ERROR: auth failed on module Volume1
    @ERROR: auth failed on module Volume1
    2019/12/11 10:34:23 [2173] rsync error: error starting client-server protocol (code 5) at main.c(1561) [sender=3.0.0]
    rsync error: error starting client-server protocol (code 5) at main.c(1561) [sender=3.0.0]
    2019/12/11 10:35:53 [2549] @ERROR: auth failed on module Volume1
    @ERROR: auth failed on module Volume1
    2019/12/11 10:35:53 [2549] rsync error: error starting client-server protocol (code 5) at main.c(1561) [sender=3.0.0]
    rsync error: error starting client-server protocol (code 5) at main.c(1561) [sender=3.0.0]
    2019/12/11 10:45:49 [4365] @ERROR: auth failed on module Volume1
    @ERROR: auth failed on module Volume1
    2019/12/11 10:45:49 [4365] rsync error: error starting client-server protocol (code 5) at main.c(1561) [sender=3.0.0]
    rsync error: error starting client-server protocol (code 5) at main.c(1561) [sender=3.0.0]
    2019/12/11 10:47:58 [5510] building file list
    [DEBUG]: /i-data/f6255952/ is a directory.
    [DEBUG]:  zysync -avHSO8 --exclude-from=/etc/zyxel/BackupPlanner/zysync/zysync_exclude_files --password-file=/tmp/rsync.pwd --bwlimit=0 /i-data/f6255952/ admin@192.168.2.9::Volume1/ --log-file=/i-data/.system/zysync.log --progress --delete
    sending incremental file list



    here is log from zysyncd.log

    2015/05/25 22:00:13 [start] zysync server(3172) exists, please stop it first.
    2015/05/25 22:02:42 [2975] zysync server v2.00 starting, listening on port 873.
    2015/05/25 22:05:03 [2975] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(506) [receiver=3.0.0]
    2015/05/25 22:07:50 [3012] zysync server v2.00 starting, listening on port 873.
    2015/05/26 00:29:29 [3386] zysync server v2.00 starting, listening on port 873.
    2015/05/26 00:32:17 [3386] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(506) [receiver=3.0.0]
    2015/05/26 00:35:29 [3361] zysync server v2.00 starting, listening on port 873.
    2019/11/18 14:26:55 [16792] generate zysync server config
    2019/11/18 14:26:56 [16792] name lookup failed for 192.168.1.254: Name or service not known
    2019/11/18 14:26:56 [16792] connect from UNKNOWN (192.168.1.254)
    2019/11/18 14:26:56 [16792] module-list nick request from UNKNOWN (192.168.1.254)
    2019/11/18 14:26:56 [16792]  send_listing enter 
    2019/11/18 14:26:56 [16792]  Volume1       
    2019/11/18 14:26:56 [16792]  send_listing exit 
    2019/11/18 14:26:56 [16792] unknown module '' tried from UNKNOWN (192.168.1.254)
    2019/11/18 14:26:56 [16825] generate zysync server config
    2019/11/18 14:26:56 [16825] name lookup failed for 192.168.1.254: Name or service not known
    2019/11/18 14:26:56 [16825] connect from UNKNOWN (192.168.1.254)
    2019/11/18 14:26:56 [16825] remote standard rsync login successfully. (host: UNKNOWN, addr: 192.168.1.254, user: admin, secret: ****, pass: ****)
    2019/11/18 14:28:55 [17178] generate zysync server config
    2019/11/18 14:28:56 [17178] name lookup failed for 192.168.1.254: Name or service not known
    2019/11/18 14:28:56 [17178] connect from UNKNOWN (192.168.1.254)
    2019/11/18 14:28:56 [17178] rsync auth failed on module Volume1 from UNKNOWN (192.168.1.254): password mismatch -> try zysync
    2019/11/18 14:28:56 [17178] remote zysync login successfully. (host: UNKNOWN, addr: 192.168.1.254, user: admin, pass: ****)
    2019/11/18 20:05:50 [2293] generate zysync server config
    2019/11/18 20:05:53 [2293] name lookup failed for 192.168.1.254: Name or service not known
    2019/11/18 20:05:53 [2293] connect from UNKNOWN (192.168.1.254)
    2019/11/18 20:05:53 [2293] rsync auth failed on module Volume1 from UNKNOWN (192.168.1.254): password mismatch -> try zysync
    2019/11/18 20:05:53 [2293] remote zysync login successfully. (host: UNKNOWN, addr: 192.168.1.254, user: admin, pass: ****)
    2019/11/19 12:48:17 [3361] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(506) [receiver=3.0.0]
    2019/11/19 12:50:33 [3473] zysync server v2.00 starting, listening on port 873.
    2019/11/19 13:16:07 [18930] generate zysync server config
    2019/11/19 13:16:07 [18930] name lookup failed for 192.168.1.254: Name or service not known
    2019/11/19 13:16:07 [18930] connect from UNKNOWN (192.168.1.254)
    2019/11/19 13:16:07 [18930] rsync auth failed on module Volume1 from UNKNOWN (192.168.1.254): password mismatch -> try zysync
    2019/11/19 13:16:07 [18930] remote zysync login successfully. (host: UNKNOWN, addr: 192.168.1.254, user: admin, pass: ****)
    2019/11/19 13:43:26 [3374] generate zysync server config
    2019/11/19 13:43:26 [3374] name lookup failed for 192.168.1.254: Name or service not known
    2019/11/19 13:43:26 [3374] connect from UNKNOWN (192.168.1.254)
    2019/11/19 13:43:26 [3374] rsync auth failed on module Volume1 from UNKNOWN (192.168.1.254): password mismatch -> try zysync
    2019/11/19 13:43:27 [3374] remote zysync login successfully. (host: UNKNOWN, addr: 192.168.1.254, user: admin, pass: ****)
    2019/11/19 13:50:45 [6048] generate zysync server config
    2019/11/19 13:50:45 [6048] name lookup failed for 192.168.1.254: Name or service not known
    2019/11/19 13:50:45 [6048] connect from UNKNOWN (192.168.1.254)
    2019/11/19 13:50:45 [6048] rsync auth failed on module Volume1 from UNKNOWN (192.168.1.254): password mismatch -> try zysync
    2019/11/19 13:50:46 [6048] remote zysync login successfully. (host: UNKNOWN, addr: 192.168.1.254, user: admin, pass: ****)
    2019/11/19 14:05:44 [3473] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(506) [receiver=3.0.0]
    2019/11/19 14:23:52 [3359] zysync server v2.00 starting, listening on port 873.
    2019/12/11 10:43:02 [3359] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(506) [receiver=3.0.0]
    2019/12/11 10:44:52 [3374] zysync server v2.00 starting, listening on port 873.
    2019/12/19 10:49:00 [3374] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(506) [receiver=3.0.0]
    2019/12/19 10:50:53 [3291] zysync server v2.00 starting, listening on port 873.
    2019/12/19 10:57:50 [3300] zysync server v2.00 starting, listening on port 873.
    2019/12/19 23:45:52 [3305] zysync server v2.00 starting, listening on port 873.

  • eozrocwd
    eozrocwd Posts: 58  Ally Member
    zysync.log
    ．2019/12/11 10:47:58 [5510] building file list
    ．[DEBUG]: /i-data/f6255952/ is a directory.
    ．[DEBUG]:  zysync -avHSO8 --exclude-from=/etc/zyxel/BackupPlanner/zysync/zysync_exclude_files --password-file=/tmp/rsync.pwd --bwlimit=0 /i-data/f6255952/ admin@192.168.2.9::Volume1/ --log-file=/i-data/.system/zysync.log --progress --delete
    ．sending incremental file list

    It seems no start backup process.
    I saw you backup whole NAS542 volume to NAS326. Has NAS326 enough space?
    Can you try to simply only backup one folder for testing this problem?
    And is possible to provide the screenshots about backup job setup/setting/steps to clarify it?
  • taceto32
    taceto32 Posts: 8  Freshman Member
    i tried backup only one folder witout success...nas326 has same hd as 542, i have created same folders and permissions but backup not start...screenshots of planner options is in previous post

Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）