NAS200 backup using JAC firmware

Discussion in 'Cisco/Linksys Network Storage Devices' started by 5circles, Apr 25, 2016.

  1. 5circles

    5circles Network Guru Member

    I'm trying to make a backup of my NAS200. I've been running Grsync from a Linux box, but it is very slow (over a week to transfer 200G, less than half). No real surprise on speed.

    So I thought I'd try backing up from the command line to an external USB drive. Then I could create a good start on the Linux box and use Grsync for updating.

    I tried
    tar -cvzf /harddisk/volume_6/data/HDD_2_1/directory.gz /harddisk/volume_2/data/directory.

    This generated
    tar: "Names longer than 100 chars not supported."

    Then I tried
    cp -a /harddisk/volume_2/data/public/directory /harddisk/volume_6/data/ HDD_2_1/

    This generated
    cp: unable to preserve ownership of `/harddisk/volume_6/data/HDD_2_1/directory/subdirectory/.../file': Operation not permitted

    It looks like I'm stuck with grsync, or I'll have to take the drive out.

    Is there a better approach?

  2. jac_goudsmit

    jac_goudsmit Super Moderator Staff Member Member

    The fastest way if you're using Linux on another system, is to shut the NAS200 down, take the hard disk out and connect it to that other system (if you're using RAID 0 you'll need both drives and the other system will need mdadm to access the disks). Only the first partition on the drive has data, the other two partitions are for configuration data and swap space.

    The "names longer than 100 chars" problem may be possibly solved by changing to the /harddisk/volume_2/data directory first, and then changing the tar command to use "." as source path. This will also save save space in the tar file.

    Another thing that may be possible (I didn't test this and it's been a long time since I did things like this) is to transfer the backup over the SSH or Telnet connection. From your (non-NAS200) Linux system, you would do something like: ssh root:password@nas200 "tar -c ." | bzip2 >backup.tar.bz2. The ssh server on the NAS starts the tar command and generates output on the standard output device, which gets transferred to the network, and piped to bzip2 which compresses the output into a file on your Linux system. Obviously some precautions are necessary to make sure that nothing goes wrong (you may want to do a dry-run by running the tar command on an interactive shell on the NAS and redirecting the output to >nul to make sure no errors occur).

    Send me a PM if you have more questions. I rarely check this forum anymore, I moved on to other things (see e.g.

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice