NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Other Backup Solutions
357 Topics
Crashplan for Dummies, aka Step by Step :)
I have just went through this and have seen several folks post that they wish there was an all inclusive guide, I just bought a Pro 2 and so far I am pleased with what I see under the hood (looks like debian to me, kernel 2.6.37) I'm a *nix guy so I thought I would try to make an all inclusive step-by-step to help anyone that might want to try and install crashplan. So here goes, the normal warning goes here - There are no warranties implied or otherwise, DO THIS AT YOUR OWN RISK! If you find any thing that needs to be updated or doesn't make sense please post and let me know... I am not the only one to post how to do this see here - http://www.readynas.com/forum/viewtopic.php?f=61&t=18139&start=15#p297737 and here http://support.crashplan.com/doku.php/how_to/configure_a_headless_client Steps for x86 ReadyNas Only: Old way,still works but uses java 6, which is out of date: 1. See Step one below 2. See Step two below 3. See Step three below 4. Once logged onto your readynas as "root" your ready to get the the software setup. Keep in mind that when you are running as root, you have elevated priviliges and you can do anything you want, including messing things up, so go slow and take your time :) - First thing we need to do is edit the sources.list, we are going to use vi which is not a friendly editor but is installed on any base *nix system and in this case will get the job done. Lets edit the file, at the prompt - vi /etc/apt/sources.list, arrow down to the last line and then arrow over to the last letter and hit the "a" button for append and then hit "enter" to get a new line and then paste "deb http://archive.debian.org/debian-backports etch-backports main non-free" . - To get out of vi and save the file "shift:" will get you the colon prompt at the bottom, then to save and exit enter "x", if you made a mistake and you do not want to save your work at the colon enter "q!" and that will quit without saving any changes. Once you exit and save your sources list should look like this, "more /etc/apt/sources.list" - deb http://www.readynas.com/packages 4.2.19/ deb http://archive.debian.org/debian etch main deb http://archive.debian.org/debian-backports etch-backports main non-free 5. Now we need to update our package list and install Java. - enter "apt-get update" - Now we need to modify configuration dialog selection so we can accept the java Terms and conditions. - enter "dpkg-reconfigure debconf" This will ask you to select a dialong frontend, select option 1 - Dialog, then it will ask you for the level, select option 3 - Medium. - Now lets install java, enter "apt-get install sun-java6-jre", it will download the package and start to install it where it will ask for you to accept the terms and conditions, select yes and complete the installation. - Modify the deb configuration and change it back, enter "dpkg-reconfigure debconf" This will ask you to select a dialong frontend, select option 6 - Noninteractive, then it will ask you for the level, select option 3 - Medium (not sure if this was the default). Updated JAVA install, credit goes to InterClaw :) The full instructions can be found here - http://minimserver.com/ejre-installer.html I will try to list just the steps for x86 ReadyNas: 1. Go to Oracle and down load the latest embeeded java version l@@k for this version - x86 Linux Small Footprint – Headless - http://www.oracle.com/technetwork/java/embedded/downloads/javase/index.html *Note you will have to accept Oracles Terms and Conditions and create an account to download the file 2. Download file and copy the java file to /c/backup/ on your ReadyNas 3. Download the EJRE Readynas Addon see the link above for the full instructions, the addon can be found here - http://minimserver.com/downloads/EJREInstaller-0.10-readynas-x86.bin 4. Install EJRE Addon and this will install the java version that you placed in /c/backup/ 5. Verify that java is working, time to jump to the command line to finish the installation. Install the Enable Root SSH addon - http://www.readynas.com/download/addons/x86/4.2/EnableRootSSH_1.0-x86.bin Complete installation by rebooting your readynas. 6. You will need to get a ssh client for your desktop/laptop, here is one for winblows (putty) - http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe, nothing to install, just download and place on your desktop or somewhere you can find it. 7. Open putty and SSH into your readynas, enter the IP address and when it prompts for username enter "root" and then your normal raidar/frontpage "password". Once logged in verify java operation by entering the following : java -version 8. Now we can install Crashplan. - Download the latest linux crashplan version enter "wget the latest version that is listed on crashplan for linux, see below" Here is the main download page, just make sure you get the latest version - http://www.crashplan.com/consumer/download.html?os=Linux, this will download andplace this in your root directory. 9. Once the diownload has completed lets extract the files which are tarred and zipped. enter "tar -xvf CrashPlan_3.0.3_Linux.tgz" or whichever version you downloaded, this will extract all of the files and place them in a folder called "CrashPlan-install". enter "cd "CrashPlan-install" and then run the installer, enter "./install.sh", this will start the installer ask for you to accept the terms and conditions and ask questions where to install etc..You can accept the defaults for most, however when it prompts you for the default crashplan backup directory, you can go with the default or provide a directory that you have already established for that purpose, e.g., "/crash-backup" whatever your share that you created without any slashes, this actual is a pointer to "crash-backup -> /c/crashplan-backup" Here are the questions, most you accept the defaults, in this case I chose to specify a different Directory - Do you accept and agree to be bound by the EULA? (yes/no) yes What directory do you wish to install CrashPlan to? [/usr/local/crashplan] What directory do you wish to link the CrashPlan executable to? [/usr/local/bin] What directory do you wish to store backups in? [/usr/local/var/crashplan] /crash-backup What directory contains your SYSV init scripts? [/etc/init.d] What directory contains your runlevel init links? [/etc/rc2.d] Your selections: CrashPlan will install to: /usr/local/crashplan And put links to binaries in: /usr/local/bin And store datas in: /crash-backup Your init.d dir is: /etc/init.d Your current runlevel directory is: /etc/rc2.d Is this correct? (y/n) [y] y 10. Configure crashplan on the readynas, in order to do this you need to download and install crashplan on a local PC, using linux, winblows or Mac - http://www.crashplan.com/consumer/download.html once that has been done we need to tunnel from the PC to the readynas, the already have this detailed on the crashplan site called a headless install - http://support.crashplan.com/doku.php/how_to/configure_a_headless_client *Note while configuring the Crashplan client -the client will show your shares twice - as links (with an arrow as part of the icon) and under the "C" folder. It won't back up the links, you need to select the folders under the "C" folder. If you try the other way, the backup "succeeds", but doesn't back anything up. Thanks to StephenB for this update! Once the configuration is complete you should be good to go.. :) I'm sure I have left something out or not fully explained something, if so let me knoiw and I will update the posting.. Good Luck :)24KViews0likes306CommentsCrashPlan Cheat Sheet and Tweaks
lBelow are Command Codes, Tweaks and info on CrashPlan. If you need me to add any more or if something changes feel free to let me know and I will adjust it. #As of CrashPlan 4.2, CrashPlan will install their Java to run with their software on you NAS. There is no need to install a new Java on your whole NAS. (In other words EJREInstaller-0.20-readynas-x86.bin by MinimServer is not needed for this install anymore). #In /usr/local/crashplan/install.vars the JAVACOMMON=/usr/local/crashplan/jre/bin/java. #CrashPlan tests their software with that specific Java. (Unless you want to do their Quality Assurance for them on a new Java :) ) #If the EJRE addon is already installed on your system DO NOT UNINSTALL IT, it is still needed globally and as per MinimServer. Uninstalling the Java runtime To remove the EJRE installation from your ReadyNAS, remove the EJRE Installer add-on. This removes the installed EJRE files, but doesn't remove the original EJRE .tar.gz file from the backup share. #Seeing What Port NAS is Listening to. netstat -na | grep LISTEN | grep 42 #Return code should look something like this: tcp6 0 0 :::4242 :::* LISTEN tcp6 0 0 ::ffff:YOUR.NAS.IP.ADDRESS:4243 :::* LISTEN #Starting,Stopping CrashPlan. #/usr/local/crashplan/bin/ ./CrashPlanEngine stop ./CrashPlanEngine status ./CrashPlanEngine start ./CrashPlanEngine restart OR /etc/init.d/crashplan [same options as above] #Unpacking CrashPlan to install. #/root/ tar -xvf CrashPlan_4.3.0_Linux.tgz #(4.3.0 change to package number you are installing) #Installing and Uninstalling CrashPlan (This will not uninstall your .ui_info or .identity file). #/root/CrashPlan-install/ ./CrashPlan-install/install.sh ./CrashPlan-install/uninstall.sh -i /usr/local/crashplan/ #/usr/local/crashplan/conf/my.service.xml <serviceHost>YOUR.NAS.IP.ADDRESS</serviceHost> OR #To have CrashPlan listen on all network interfaces and thus accepting GUI connections from any computer on your home network. <serviceHost>0.0.0.0</serviceHost> #"If Watch file system in real time" is not working CrashPlan suggested changes so that it works on a NAS. #/etc/sysctl.conf fs.inotify.max_user_watches=1048576 #Increasing Memory Value to CrashPlan Engine. #Go to CrashPlan on PC and Double Click Home Icon in Upper Right Hand Corner #Value should be in memory increments of 64, increasing value too high will stop CrashPlan from running. The upper limit on my NAS PRO Business is 3072 and I have 8 GB of Ram installed. java mx "value" OR #Stop CrashPlan #Edit /usr/local/crashplan/bin/run.conf in SRV_JAVA_OPTS change "-Xmx3072m" to desired value. #Start CrashPlan #Configuring CrashPlan Backup set to Exclude all Directories Named "Recycle Bin". #Located in Settings-Backup-File exclusions:-Configure (Make sure "Regular Expressions" is checked). ./*Recycle Bin.* #CrashPlan updated to 4.3.0 and now my Windows 7 GUI will not connect. 1) Make sure Windows 7 GUI is 4.3 and make sure it is not running when you are doing the steps below: 2) Copy your .ui_info from your NAS to your desktop: a) .ui_info on NAS is probably located /var/lib/crashplan (unless you changed it from the default when installing i.e. What directory do you wish to store backups in? [/usr/local/var/crashplan]) b) .ui_info on your desktop is located C:\ProgramData\CrashPlan. (Rename your old .ui_info to .ui_info.orig) 3) Configure your ui.properies file on you PC appropriately. i.e. service port should be 4200 if you are using ssh to tunnel or service host should be changed to your NAS ip address if you made the proper changes in the my.service.xml file on you NAS. 4) Start up CrashPlan 4.3 on your desktop. #Another way to check if the CrashPlan service is running in your PC. ps auxww |grep -i CrashPlanService #Return code should be something like this: root 19952 80.3 7.4 3623440 611904 ? SNl 08:17 400:32 /usr/local/crashplan/jre/bin/java -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx3072m -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false -classpath /usr/local/crashplan/lib/com.backup42.desktop.jar:/usr/local/crashplan/lang com.backup42.service.CPService root 23519 0.0 0.0 4104 504 pts/0 S+ 16:35 0:00 grep -i CrashPlanService #Installing the CrashPlan app instructions from CrashPlan's Website. CrashPlan Headless Client Install ReadyNas Forum - Crashplan for Dummies, aka Step by Step (this is the latest guide so far out of the 18 or so pages in the post). Crashplan for Dummies, aka Step by Step :)19KViews0likes34Comments
Crashplan JRE update needed
Crashplan released an update on 21 September 2015 (4.4.0) which fails to install on my pro-6 (running 4.2.28). The issue is that the new service requires jre 1.7 or jre 1.8, and my system was running 1.6. The upgrade not only repeatedly failed, it also filled the OS partition with repeated downloads. So if you are running crashplan on OS 4.2.x, then take a look right away. You can install jre 1.8 on the NAS - I used the procedure here: http://minimserver.com/ejre-installer.html Crashplan has not tried up upgrade since I installed the jre - I'll update the thread after that happens.Solved17KViews1like85Comments
CryptoLocker and a backup strategy
I am requesting the community to evaluate and criticize this approach to CyberLocker We are basically a Windows shop and we are scared to death about the CyperLocker virus. From what I read, it is almost impossible to detect the virus/malware and it infects lots of systems because workers are curious, naive, or dumb. Our judgement is that we will get hit eventually. Mapped drives are the essence of our internal networking strategy for all of our locations. All of the mapped drives in the Windows workstations point to shares on the ReadyNAS device. As far as I can tell we are perfect candidates for CyberLocker to scramble our data. StephenB provided a good idea in a prior 2013 exchange on this topic -- use file read only folder permissions to repel CyberLocker changes for the backup folders which are located on a local workstation. It was a great idea and we have been using that approach for the past two years. Now, the trade press is discussing how the malware has evolved -- one reviewer said it looked like a software business with revisions and point releases and a collections department. As the capability gets better storage of backups within the workstation environment seems less appropriate since changing file permissions is fairly trivial in the Windows environment. In order to avoid the issue we are now considering upgrading our ReadyNAS units to include another set of disks (RAID 1) and using them for backup instead of having the backup stored on a robust workstation. The idea is to use the ReadyNAS backup capability to copy the data to non-mapped areas that are created with the “hide directory” option enabled -- a CIFS designation. This would establish a set of a set of hidden folders in the Windows environment that still could be accessed if the precise device/folder UNC path was specified in File Explorer. We would use the ReadyNAS backup capability for night-time backup. In case of infection by CyberLocker we would have a recent backup that is not encrypted. An additional precaution is to create seven (or more) ReadyNAS backup jobs – one for each day of the week. That way we would have the essential equivalent of a seven day backup cycle in case the most recent backup fails. Any comments would be appreciated. BTW, we have implemented off-site storage for the case of theft or destruction of the NAS unit. That component of our backup is not considered in this discussion.Solved15KViews0likes22CommentsMemeo backup premium. Automatic activation - how to
Hello everyone, I have finally made my Memeo Backup Premium activate itself. I had been searching this forum for answers, found none. I found a lot of people complaining about Netgear support on this topic. I will not describe the problem and a solution... 1. The not working setup What is the problem... When you start Memeo application (usually starts with you system) you can go to the log file. Right-click you Memeo icon in system tray and choose: "Send Log Files". A new e-mail is created in your e-mail client with two attachments, log and xml file. Open the log file. You will see something like this: Start Time: 2012-03-28 19:21:24 ====================================================== I: 2012-03-28 19:21:24 (tid BMUMonitorApp) - Searching for: UpnpSearcher I: 2012-03-28 19:21:40 (tid BMUMonitorApp) - DataString: HTTP/1.1 200 OK Cache-Control: max-age=1800 ST: upnp:rootdevice USN: uuid:4d696e69-xxxxxxxxxxxxxxxxxxxxxxxxxxx::upnp:rootdevice EXT: Server: Linux/2.6.15-1.2054_FC5 UPnP/1.0 miniupnpd/1.0 Location: http://192.168.1.1:5555/rootDesc.xml ... I: 2012-03-28 19:21:42 (tid BMUMonitorApp) - DataString: HTTP/1.1 200 OK CACHE-CONTROL: max-age=1800 DATE: Wed, 28 Mar 2012 17:21:34 GMT EXT: LOCATION: http://192.168.1.1:49152/wps_device.xml SERVER: Unspecified, UPnP/1.0, Unspecified ST: urn:schemas-wifialliance-org:service:WFAWLANConfig:1 USN: uuid:00000000-0000-1000-0000-xxxxxxxxxxxxb::urn:schemas-wifialliance-org:service:WFAWLANConfig:1 I: 2012-03-28 19:21:42 (tid BMUMonitorApp) - DetectExternalDevice::IsConnected() - NASes found = 0 I: 2012-03-28 19:21:42 (tid BMUMonitorApp) - BMUMonitorShell::ConfigureIfNecessary() - Registered online user = ConsumerKey = xxxxxxxxxxxxxxxxxxxxx, ConsumerSecret = xxxxxxxxxxxx, AccessToken = xxxxxxxxxxxxxxxxxx, AccessTokenSecret = xxxxxxxxxxxxxxxxxxxxx, Username = john.smith, ClientEmail = john.smith@gmail.com I: 2012-03-28 19:21:42 (tid BMUMonitorApp) - BMUMonitorShell::RegisterExternalDevice() - Trying to detect external drives I: 2012-03-28 19:21:42 (tid BMUMonitorApp) - DetectExternalDeviceManager::ExternalDeviceWasDetected() - Valid external drive detected = False ... "Valid external drive detected = False" :( So... now we will make it work. 2. The working setup What is different? The laptop and the ReadyNas are now directly connected with an Ethernet cable. What you need to setup is a) enable ETH 1 on ReadyNas (in GUI it is called Ethernet 2) b) assign an IP to that interface (different that the subnet used on ReadyNas ETH 0) c) configure a static IP on your laptop (from the same subnet as above). No gateways or DNS needed here. d) make sure that you can access ReadyNas web page e) shut down Memeo Backup Premium f) Connect you laptop to your WiFi network (this is the usual way I use at home) g) you should be able to access internet now, test it h) turn off laptop firewall i) start Memeo Backup Premium Lets have a look at the log now... I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - DataString: HTTP/1.1 200 OK ST:upnp:rootdevice USN:uuid:xxxxxxxxxxxxxxxxxxxxxxxxxxx::upnp:rootdevice Location:http://192.168.1.5:2869/upnphost/udhisapi.dll?content=uuid:xxxxxxxxxxxxxxxxxxxxxxxxxxx OPT:"http://schemas.upnp.org/upnp/1/0/"; ns=01 01-NLS:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Cache-Control:max-age=900 Server:Microsoft-Windows-NT/5.1 UPnP/1.0 UPnP-Device-Host/1.0 Ext: I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - Found device at: http://192.168.1.5:2869/upnphost/udhisapi.dll?content=uuid:xxxxxxxxxxxxxxxxxxxxxxxxxxxx I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - Parsed device as: 192.168.1.5:2869 I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - DetectExternalDevice::IsConnected() - NASes found = 0 I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - BMUMonitorShell::ConfigureIfNecessary() - Registered online user = ConsumerKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxx, ConsumerSecret = xxxxxxxxxxx, AccessToken = xxxxxxxxxxxxxxxxxxxxxxxxxxx, AccessTokenSecret = xxxxxxxxxxxxxxxxxxxxxx, Username = john.smith, ClientEmail = john.smith@gmail.com I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - BMUMonitorShell::RegisterExternalDevice() - Trying to detect external drives I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - DetectNetGearExternalDevice::HadValidDevice() - NetGear drive connected, product ID = ReadyNAS, vendor ID = NasDevice, serial no = I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - DetectExternalDeviceManager::ExternalDeviceWasDetected() - Valid external drive detected = True I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - BMUMonitorShell::RegisterExternalDevice() - External drives found, trying to auto-register I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - URL = http://register.memeo.info/register3.php I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - date_time = 03-28-2012 xxxxxxx I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - hkey[] = ReadyNAS I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - email = john.smith@gmail.com I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - p = 0 I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - b = 0 I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - u = 1 I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - buildtype = ng I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - uid = xx:xx:xx:xx:xx:xx I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - lang = en-US I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - eid = xxxxxxxxxxxxxxxxx I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - vers = 4.60.0.7xxx I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - prod = autobackuppro I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - os = Unknown I: 2012-03-28 20:40:29 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Register variables - prod_level = PREMIUM I: 2012-03-28 20:40:37 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Server response = <?xml version="1.0" encoding="utf-8"?> <Registration><Result>Success</Result><ProductKey>MEMNTGR000-xxxxxxxxxxxxxxxxxxxxxx</ProductKey><ValidProduct><PID>ReadyNAS</PID><VID></VID><model_name></model_name></ValidProduct></Registration> I: 2012-03-28 20:40:37 (tid BMUMonitorApp) - RegisterExternalDevice::RegisterProduct() - Registered. Product key = MEMNTGR000-xxxxxxxxxxxxxxxxxxx I: 2012-03-28 20:40:39 (tid ) - EngineController::mCheckNetworkTimer_Elapsed() - Getting network paths to find match for disconnected network plans I: 2012-03-28 20:40:39 (tid ) - EngineController::FindNetworkPathsForPlans() - No network paths found I: 2012-03-28 20:40:39 (tid ) - EngineController::mCheckNetworkTimer_Elapsed() - Retrying for 1 disconnected network plans I: 2012-03-28 20:40:40 (tid BMUMonitorApp) - BMUMonitorShell::CreateSubscriptionPlanInfo() - {"stat":"ok"} I: 2012-03-28 20:40:40 (tid BMUMonitorApp) - TimeBomb::CreateRegistryTimeBomb() - Set expiration date = 03/04/2112 20:40:40, key = ExpirationDatePremium I: 2012-03-28 20:40:40 (tid BMUMonitorApp) - TimeBomb::CreateRegistryTimeBomb() - Set TimeBomb to expire in 36500 days, key = ExpirationPremium I: 2012-03-28 20:40:40 (tid BMUMonitorApp) - BMUMonitorShell::DefuseTimeBomb() - Software is registered Software is registered :) We are done! Conclusions: 1) why some packets are blocked when using the first (not working setup)? I have checked my router logs, but I did not find any information. LAN 1 and LAN 2 should work like a switch, but apparently they don't 2) you will need to connect you laptop directly to ReadyNas, and to your wireless router. The second connection is used to access internet, to be able to register your product. 3) The above may be a problem on PCs with only one Ethernet interface. I assume that getting a simple Ethernet switch (no filters/firewall) should help. I do not have any to check. Have fun! :wink:12KViews0likes15CommentsWindows Sever Backup to SMB error "THe username not recognized by local computer"
I have a Server 2012 machine that's in a workgroup so no AD involved. When I tried to create a backup schedule all goes well until I try to authenticate it says that "the User name being used for accessing the remote share folder is not recognized by the local computer" I believe this problem can be resolved if my server was a DC and the NAS was set to authenticate using AD. But I don't want/need this Any work around this?11KViews0likes4CommentsRsync Backup job NAS to USB drive suddenly displaying strange behaviour
The backup job in question has been running flawlessly 3 times a day for the last year.(alongside a similar job which is not mis-behaving) The only change I have made since this began is installing OS 6.7.4 The settings are: The Source Type is "volume" and the Name is "volume: data" Everything else is blank. The Destination is Type "remote" and the Name is "remote: RSync Server", Host is "localhost" and Path is "USB_HDD_1/NAS_IAN_Backup" Under Advanced compression is disabled and Remove deleted files on target is checked. The USB Drive is NTFS format. The odd behaviour is as follows: The log shows the log as starting and completing within one second !!! and reports Backup Status: Success Which is clearly not correct. The log also shows the following: sending incremental file list sent 733 bytes received 41 bytes 1,548.00 bytes/sec total size is 2,930 speedup is 3.79 S): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/Documents, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/Downloads, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/Ians_Stuff, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/Music, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/PC_Backup, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/Pictures, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/Recovered_Data, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/Transmission, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/Videos, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/couchpotato, ACL_TYPE_ACCESS): Operation not supported (95) rsync: set_acl: sys_acl_set_file(data/sickrage, ACL_TYPE_ACCESS): Operation not supported (95) data/Documents/ data/Downloads/ data/Ians_Stuff/ data/Music/ data/PC_Backup/ data/Pictures/ data/Recovered_Data/ data/Transmission/ data/Videos/ data/couchpotato/ data/sickrage/ sent 838 bytes received 1,308 bytes 4,292.00 bytes/sec total size is 2,930 speedup is 1.37 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.1] I am totally stumped by this and am hoping someone here can help me or better still provide a solutionSolved11KViews0likes20Comments
Using ReadyNAS Replicate with OS 6.5.0
I am using Replicate to backup from my RN312 to a RN104. Both devices have been upgraded from latest 6.4 to 6.5.0. I am not able to get Replicate working again. Is there some documentation? Problems so far: - on the Cloud tab, I remember there was something like "Remote". Can't find it anymore. - instead, I tried to set up ReadyCloud. Is that the right way? - ip v4 no longer works for my installation. I have to use ip v6 on both devices. Otherwise they are not able to connect to ReadyCloud. Strange. I can not go back to v4, really? - I can no longer login on the webbage replicate.readynas.com. The login page asks for a Remote ID. Is that new? I have a Replicate username / password, but it no longer works since yesterday or so. Also, it is not possible to log in with MyNetgear credentials. Did I overlook something... Best regards, MartinSolved11KViews0likes13Comments
How does RSYNC "verify" integrity of a backup???
I have performed a factory reset my ReadyNAS Pro Pioneer (RNPP) unit. and now want to ensure the restore of the original data from an external USB drive (connected to the NAS' USB port) is copied without any data corruption. I am trying to confirm color=#0000FF]whether RSYNC is a good tool to use to verify the copied data's integrity[/color]. I have ready many posts that suggest using RSYNC to verify a backup. One such example: viewtopic.php?f=66&t=51339&p=292769 mdgm wrote: ... After doing the backup to the USB disk you can verify it using a Rsync backup to USB disk My questions are:' 1) After the initial restore to the RNPP unit (using FrontView's backup job, Source=Share-USBDrive; Target=Share-RNPP Share Drive), I set the backup type to RSYNC. Do I then perform a FULL backup again? 2) The expectation is nothing changes during this first RSYNC backup. Question - so, how does RSYNC actually verify the backup? Does it to a byte-for-byte comparison or just a date/time comparison?10KViews0likes23CommentsBackup using rsync – what options are used
Rsync is a robust Linux file copy program with lots of options http://linux.die.net/man/1/rsync is a great discussion of the features and options. . http://serverfault.com/questions/138287/how-does-rsync-does-incremental-backups is a thread that discusses rsync. The effect is that Rsync does not do true incremental backup but instead captures the state of the file differences from a base copy at the time of the backup operation. The Netgear documentation regarding backup is sparse. The ReadyNAS backup capability is a GUI for the most common file copy needs. The Netgear documentation discusses incremental backup but that is not what happens since there are no lots of incremental files created. What actual rsync options are enabled during a Netgear copy? Bsckground The terms ‘incremental’ and differential’ backup deal with having a base level copy of a set of files and then maintaining the difference between the data today and the base. Incremental backups track the difference between the base and essentially build on each other. For example if there are five incremental backups to restore the file the backups must be restored sequentially as they were taken – first #1, then #2, etc. The amount of data in each increment is typically less than other methods. In robust File backup software, this is accomplished by log files, and associated data that is captured. Differential backups track the difference between the base and what the current state is today. Each time a differential backup is taken, all of the changes that have occurred are contained in the backup data. To restore the data only the most recent version of the ‘difference’ needs to be restored. The amount of data in each differential backup typically gets larger as the changes accumulate. In both scenarios there typically is a complete base level copy done periodically so there are no differences and the process of incremental/differential backup start again. Purges of old data need to occur. Some backup programs do thls automatically.Solved10KViews0likes14Comments
