Here are a few key differences:
X-RAID (Sparc) volumes use the 16k block size (if last factory default was on RAIDiator 4.x or later. This is the case for the Duo v1 unless disks were migrated from an older Sparc ReadyNAS last factory reset on older firmware).
X-RAID uses a parity disk. That disk doesn’t have a partition table on it. If you want to attempt data recovery using Linux you’ll need to use the other disk(s).

X-RAID2 (ARM and x86) volumes use the standard 4k block size. This makes it a little easier to recover you data in Windows or Linux.

X-RAID2 volumes have distributed parity. To recover your data you need X-1 working disks where X is the number of disks in the array. Or in a 6-bay or greater ReadyNAS if using dual-redundancy you need X-2 disks.

Here’s how to mount an X-RAID2 array (ARM or x86 ReadyNAS) in x86 Linux:

# sudo su
# apt-get install lvm2
# mdadm –assemble –scan
# vgscan
# vgchange -ay c
# mount /dev/c/c/ /mnt

In the above example we mount the volume to “/mnt”. We could o course mount it to any empty directory we like.

DUO – USB ports one above the other or side by side
NV+ – Does it have a kettle lead at bottom or power connector at top?

Interesting reading though and explains why when backing up my Duo it lists USB ports as top and bottom when actually they are left or right

Always good to get feedback, positive or negative.

Have you enabled root SSH access? If you have SSH access you could SSH in and check the backup job progress.

Maybe a bug?

I am using localhost for the host, and USB_HDD_1 for the path, also, as noted in the instructions above.

No option for no full backups, or full backup up every 8 weeks. Once per month is too frequent.

Also, what happens if the backup drive is full?

I’m trying to find a recovery service for my infrant nv nas. I’ve been in contact with netgear, but there was no menction of a recovery service.

Do you have any info on how I can contact and contract with an experience service provider?

Thanks

Josh

Otherwise you’ll need to seed the backup which is more complex (if using Frontview backup you’ll need to do a dummy full backup e.g. of single file to test share then change backup job properties. As full backup has been done, NAS will attempt to do an incremental backup on next run if set to full backup first time only).

I’m not sure whether or not that JBOD unit will be properly recognised or not. if it is then hopefully it’ll work fine.

I recommend formatting USB disks to use EXT3 and also enabling fast USB writes

I recommend doing an ordinary USB backup using Frontview then changing to use Rsync. Rsync is slow for full backups, but it’s great for incrementals and verifying a full backup

Rsync is good to use and I recommend it.

A real newbie here…. You have prepared a great resource here, thanks.

A quick question: I am wishing to backup my Duo (2x 500Gb) to a USB connected JBOD unit ( total 1Gb capacity), before I upgrade the Duo to 2Gb HDDs.

Is Rsync the most the best way to do this? I don’t know, but does Rsync allow you to verify that the backup is complete and error free?

I would like to backup my NAS on a regular basis to my JBOD; again is Rsync the best tool to do this – I would prefer an automated solution.

Cheers,

Stephen

This works fine for me. I haven’t tested a restore from it but don’t see why it wouldn’t work. This doesn’t involve any hacks and is done completely via Frontview. I would expect it would be supported. In fact if backing up to a FAT32/NTFS formatted drive some may find it works better than the normal method as Rsync has a checkbox to enable FAT32 compatibility mode.

I don’t recommend doing regular full backups when using Rsync. Rsync will compare the source and the destination and ensure that they match. If you do a full backup using Rsync it’ll take a long time. That’s why I recommend doing a USB backup as one normally would in Frontview then changing to using Rsync.

If you still want to do regular full backups then my advice would be to not use Rsync and just stick to the normal Frontview method.

Is it safe to assume that my selection in the “Schedule Full Backup” drop-down list (in Step 4 of Backup > Edit Backup Jobs – First time, Every week, whatever) will have no effect on the backup job when “Remote: Rsync Server” is selected as the backup destination in Step 2?

Here are the steps to backup your entire ReadyNas (rather than just one share) to an attached USB drive:

1. Under Services > Standard File Protocols turn Rsync on.

2. Go to Volumes > USB Storage (if not found here the settings for the USB drive will be under Shares > Share Listing) and turn on Rsync for the USB drive and set the permissions. You may also want to set the Rsync login and password.

3. Go to Backup > Backup Listing, and open a backup job’s properties to edit it. Or add a Backup Job.

4. Set the Backup Source settings. Select: “Volume: C” from the menu. Leave blank the Host, Path, Login, and Password fields.

5. Set the Backup Destination settings.
Select “Remote: Rsync Server”
Set Host to localhost
Path is the Rsync exported module of the attached USB drive. Something like USB_HDD_2. It will be listed in the menu of possible destination types/locations as “Share: USB_HDD_2″. Just copy that share name into the Path field.
Login and Password as you set in Step 2.

6. Press Test Connection to make sure you have the backup job settings correct.

7. If you want the backup to be an exact mirror of the source i.e. wipe the USB HDD (or folder inside that if specified), then make sure that the “Remove deleted files on target” option is checked.

8. Check the rest of the settings and make appropriate changes (if any) then run the backup job.

It is possible that the Test Connection button will report that the connection works, however the backup will fail if the Path on the Rsync server (the Rsync exported module name) is not specified or correct. Test the backup and check the logs to make sure you have everything working.

To get a list of your ReadyNas Rsync modules, execute from the command line (terminal, etc) the command:
% rsync rsync://USER@IPADDRESS

I have random freezes on my brand new ultra 2, while copying large amounts of data to it. I suspect the memory as the cause.

When i follow the guide and do a memory test on my ultra 2, the LED’s blink in the following order, one at a time:

1. Power LED
2. USB LED
3. Disk 1 LED
4. Disk 2 LED

in a loop.

How can i tell if the memory has passed or failed?

Tia.

/Bear

Be aware that the ReadyNAS will need to wipe your disks before it can use them so if using used disks be sure to backup the data on them first

Like all other x86 ReadyNAS, the ReadyNAS Ultra 6 uses software RAID.

Regards.

Any suggestions? It’s driving me mad. I know there’s only space for three addresses but my btconnect account is the main one I use and I would like to get it there.

I much prefer backing up my Macs to a ReadyNAS than backing up to a Time Capsule. The Time Capsule has a single non-user replaceable drive. Whereas the ReadyNAS has multiple drives and X-RAID2 provides redundancy so that if a disk fails you don’t lose your backups. It would be a shame if a single disk failure meant you lost all your backups. I backup my ReadyNAS (including Time Machine backups) occasionally to another ReadyNAS which I then take off-site for protection against theft, fire, data corruption etc.

Then there’s also performance to consider. Many ReadyNAS models are much faster than the Time Capsule. For example the Ultra 6 comes pretty close to saturating gigabit ethernet. Ethernet is good for the initial full backup and if you ever need to restore your entire Mac from Time Machine or even restore onto a new machine from Time Machine.

One clarification please: When you say, “Using Time Machine on my Macs, my data is automatically backed up wirelessly!” Do you mean that you’re able to back up to the ReadyNAS wirelessly?

I currently have an Apple Time Capsule to do that because I thought it was the only way to do the backups *wirelessly*. Are you saying that you can back up with Time Machine to the ReadyNAS wirelessly?

Common migrations include from the ReadyNAS Duo to a ReadyNAS Ultra, the ReadyNAS NV+ to a ReadyNAS Ultra, a ReadyNAS NV+ to a ReadyNAS NVX, a ReadyNAS NV+ to a ReadyNAS Pro

For rackmount ReadyNAS common migrations include: ReadyNAS 1100 to a ReadyNAS 2100, a ReadyNAS 1100 to a ReadyNAS 3100, a ReadyNAS 1100 to a ReadyNAS 3200, or even a ReadyNAS 1100 to a ReadyNAS 4200.

Of course you can do migrations from e.g. a ReadyNAS 1100 to a ReadyNAS Pro, or a ReadyNAS NV+ to a ReadyNAS 2100 following my instructions.

Mostly I have a collection of ~1000 movies that I stream via iTunes and AppleTV.

I live in the US now, although originally from London.

I lived in Melbourne for 6 months in ’86 working with Cray at a Government site that subsequently relocated to Canberra. When I was in Melbourne I joined a local rowing club and we had a lot of fun and camaraderie.

In the early MAC OSX 10.1, 10.2 days I became a regular poster and authority using Samba to print between MAC’s and PC’s. I got a kick out of figuring out the issues and then being able to help on the forums.

From 10.3, Apple made all that work seamlessly and my “expertise” became pretty irrelevant. Plus it was taking too much of my time – all I wanted to do was print to the Mac printer from my Wife’s PC

Anyway – thanks for the good work – and you have certainly inspired me to look at the Ultra box…