NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Using with Backup to Disk Applications
128 TopicsReadyNAS becomes unresponsive - could it be tied to FW6.4 and backups?
I own a ReadyNAS 104. I currently have four 3TB drives in it in X-Raid. (5.86TB free of 8.17TB total). I have a 5TB USB 3.0 drive plugged into the front USB Drive. It is formatted as EXT4. I am only running SMB, HTTP and HTTPS services. I have 8 backup jobs to run each day (full refresh every 4 weeks). 4 are from shares on the ReadyNAS, 1 is a home directory on the ReadyNAS and 3 are remote: Windows/NAS (Timestamp). Everything was working fine. I applied the 6.4 upgrade. When the ReadyNAS first boots it works fine. Note that it did take about 3 days to complete the volume sync after the upgrade. However, after running for a while the unit stops working. I think I've narrowed it down to when one of the bigger backup jobs starts. The sympoms are as follows: I cannot access the admin page. It gives me the message that the unit is not responsive. The shares are also unavailable when this happens. There is no message on the display of the unit. The 4 drive lights are solid blue. The light on the button is flashing. I've left it this way for 2 days and it does not improve. I've tried pressing the power button on the unit and it has no effect. The only thing I can do is to unplug the readynas and plug it back in. Then it works ok, until another backup starts. Any suggestions? Anyone else experiencing similar issues? Thanks for your help.8.1KViews1like34CommentsBackup -> Source -> Remote Rsync Server -> Port
I'm using a: NAS 516 Firmware 6.1.4 And setup a "Backup -> Source -> Remote Rsync Server" Since there is nowhere in frontview to set a Port, I edited /etc/frontview/backup_jobs.conf by finding my job (backupJob), then editing the line: "<src_port>0</src_port>" and changing the 0 to the port I need to use. (default 0 means use the default port 873). This job now runs correctly using the alternative rsync port using a remote server. My questions are: 1. Will frontview add an option for the rsync server port in a future firmware? 2. If I manually edit /etc/frontview/backup_jobs.conf via the root shell login, will the system try to revert the change by any events, especially firmware upgrades. Thanks for any input.5.4KViews1like3CommentsRALUS for BackupExec
Hi, I have a problem with my ReadyNAS. the RALUS for BackupExec doesn't work anymore. I can't see it in the favorites ressources in BE2010. It disappeared just after a backup. I don't understand why. IP address of the BE server in the NVX is correct. I have update the RALUS add on on the NAS with the Last Version but it's still the same. I connect to the NAS with SSH in the ralus.cfg , IP address is correct. I think it's a problem of "publishing" the Agent. have you got a link to download the old version of RALUS addon . Thank you. BE Server : 2008Server x64 - BE2010 NAS : ReadyNAS NVX 40003.1KViews1like2CommentsHow does Backup actually work -- files selected, best approach, etc.
I am not very knowledgeable on the LINUX environment and heritage. My question has to do with what backup method to select and how to parameterize. Windows centric folks may have some difficulty in understanding the ReadyNAS backup options – at least this Windows centric fellow. I will attempt to outline my confusion. Any help would be very useful. Typically in the Windows world (business system environment) everyone is familiar with the concept of a Backup Job and the notion that backups come in ‘sets’ that represent the initial backup and then a form of differential or incremental backup from the base set. A set can span multiple backup events (either differential or incremental) and then the process cycles around to start again. Typically there is a notion of several backup sets being saved so there is a reasonable timeframe for data recovery of files. This cycle of removing older sets is typically referred to a purging. The ReadyNAS firmware documentation uses the term ‘protocol’ regarding the backup process. I believe that refers to the transport level methods and not the backup selection process of files to be transported. Is that true?? Against that background here are the questions that puzzle me – others may be confused as well. Windows/NAS(Timestamp) – apparently refers to a backup protocol independent of the transport method. It relates to incremental backups. What is the selection algorithm for a file to be in the incremental backup set? Is there only one incremental backup produced and older incremental backups are then overwritten? One party has indicated that this method is a copy from source to destination with no icrements but I may have not understood properly. The firmware documentation indicates (ReadyNAS OS 6.2, page 199 ) talks about incremental backup. Which is currently correct?? Windows (Archive Bit) – apparently refers to a backup protocol independent of the transport method. It is covered in the 6.2 firmware manual. This option is absent from the 6.4.0 software. Is this a mistake or intentional? FTP – my view is that this would refer to a transport protocol and includes the typical client/server FTP commands. What is the selection algorithm for a file to be in the incremental backup set? Is there only one incremental backup produced and are older incremental backups are then overwritten? NFS – my view is that is a transport protocol for distributed file system but it most likely has more robust capabilities. What is the selection algorithm for a file to be in the incremental backup set? Is there only one incremental backup produced and older incremental backups are then overwritten? Rsync Server – seems to be a robust method of source/destination synching. As far as I can tell, the data to be selected is in the backup definition and the Rsync protocol offers a selection method plus allows files to be removed from the destination if they are removed from the source. What is the selection algorithm for a file to be in the incremental backup set? Is there only one incremental backup produced and older incremental backups are then overwritten? Will it work for intra-system backups, e.g. to a different volume on the same ReadyNAS device? Rsync over Remote SSH – seems to be a robust method of source/destination synching using the SSH capability/transport mechanism that offers substantially more security. As far as I can tell, the data to be selected is in the backup definition and the Rsync over Remote SSH protocol offers a different and more secure transport mechanism. In summary, I am looking for precision regarding what is selected and copied along with a notion of how the incremental capability works. Additionally the question of whether there are file differences based on the transport method is importan as well.Solved2.5KViews1like1Comment