Moving from ReadyNAS NV to Pro 6 - Best plan?

Your firmware is about 4 years old (see http://www.readynas.com/forum/viewtopic.php?f=1&t=15059).

I would suggest you:
1. Backup all data
2. Verify backup is good
3. Upgrade to latest RAIDiator on NV.
4. Install a single disk in Pro 6 (if NAS doesn't already come with disks).
5. Update Pro 6 to latest RAIDiator x86 firmware via System > Update > Remote. Depending what firmware is on the Pro 6 currently a few firmware updates may be required to get to 4.2.19
6. Power down Pro 6 and insert any other new disks you want to use in Pro 6 into it.
7. Do a factory default (e.g. via boot menu: http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu) to give yourself a clean setup on the latest firmware
8. Manually configure the Pro 6 with settings, shares etc. you used on the NV.
9. Run backup jobs to transfer data across to the Pro 6. Best to use NFS for full backup jobs and then change backup job properties to use Rsync for incrementals.
10. Once you have your new Pro 6 up and running, I would suggest you factory reset the NV (possibly with new disks as well) and perhaps use the NV as a backup NAS. A factory reset of the NV after updating to 4.1.7 or later will give 4k sector alignment which will be useful if you move to using 2TB disks eventually in the NV.

mdgm wrote:
9. Run backup jobs to transfer data across to the Pro 6. Best to use NFS for full backup jobs and then change backup job properties to use Rsync for incrementals.

I "always" seem to forget: when you setup the backup job to copy from the "NV+" to the new "Pro", that's a backup job on the NV+ --- right? i.e. pushing from the NV+ to the Pro, rather than pulling on the Pro from the NV+?

I'm moving from two NV+'s to one Pro 6 so I'm in a similar situation... although in my case I have multiple user shares, multiple timemachines, and multiple "media" shares all to be combined somehow (i.e. may combine into a single huge media share or leave it as two shares on the Pro).

You can push to the Pro from the NV+ or pull from the NV+ to the Pro. However for some things like the Easy Time Machine share (http://www.readynas.com/TimeMachine) the backup job needs to be on the source NAS.

You can specify a path in a share to backup to, so if source was say "media" share, you could specify "media/NASA" as the destination path to backup to the NASA folder on the media share.

Thanks, mdgm.

If I backup from NV+ "A" to the Pro, and then backup from NV+ "B" to the Pro:
(a) will NFS (and then rsync) add files and folders from "B" that weren't copied over from "A"?
(b) will it delete any previously copied over files/folders?
(c) how will it handle things if a file or folder exists on both "A" and "B"

mdgm wrote:
However for some things like the Easy Time Machine share (http://www.readynas.com/TimeMachine) the backup job needs to be on the source NAS.

I didn't see where in that link that it talked much about moving the TM bundle from one NAS to another. However, your response in topic http://www.readynas.com/forum/viewtopic.php?f=71&t=57771 talks about creating a share on the destintion NAS, backing it up to there, then in admin frontview moving the bundle around.

Is that how you'd still suggest moving the TM bundle?

And... since I'm combining two NV+'s into one Pro6, I'm thinking of expanding the TM bundle to allow multiple Macs to backup to it. Am I correct that I'll have to basically create a new larger bundle and then manually copy files from the old smaller bundle over to the new larger bundle -- perhaps combining this with the backup from the NV+ to a special share, then copy files from that bundle to the c/.timemachine bundles? Or is there some other / better way to expand that size of a TM share while retaining previous TM data?

(thanks!)

I still suggest moving the same way.

You have separate bundles for each Mac. Providing you're running 10.6.4 or later (I think) the sparsebundles will automatically expand to have the new limit when you've set a higher quota and next do a TM backup.

ok... so I backed up the TimeMachine from the NV+ to the Pro first with NFS (800GB takes 20 hours) and then incremental with rsync to a share called "Tmbkup". Turned on TimeMachine on the Pro, then turned it off. Then I smb'ed to the pro:admin/c and moved the sparsebundle to c/.timemachine. Then turned timemachine back on. I set my Mac's timemachine to point to the Pro and... it can enter timemachine ok. (and yes, there's another bundle there for another Mac, but I haven't tried that one yet)

However, when I tried to do a timemachine backup, it kept giving errors and trying to expand sparsebundle and deleting lots of old backups, etc. never actually backing up. Looking at console I see lots of messages e.g. (until I cancelled the backup):

1/4/12 8:34:01 PM com.apple.backupd[7853] Starting standard backup 1/4/12 8:34:01 PM com.apple.backupd[7853] Attempting to mount network destination using URL: afp://readynas@mynas.local/ReadyNAS 1/4/12 8:34:03 PM com.apple.backupd[7853] Mounted network destination using URL: afp://readynas@mynas.local/ReadyNAS 1/4/12 8:34:03 PM com.apple.backupd[7853] Error writing Time Machine Information file: /Volumes/ReadyNAS/my.sparsebundle/com.apple.TimeMachine.MachineID.plist 1/4/12 8:34:03 PM kernel ASP_TCP CheckReqQueueSize: increasing req queue from 32 to 128 entries. so 0x1d2986a0 1/4/12 8:34:03 PM kernel AFP_VFS afpfs_mount: /Volumes/ReadyNAS, pid 7854 1/4/12 8:34:03 PM com.apple.backupd[7853] Resizing backup disk image from 800.0 GB to 2125.7 GB 1/4/12 8:34:13 PM com.apple.backupd[7853] backupd: resize request 4457992024 is above maximum size 4294967216 allowed. 1/4/12 8:34:13 PM com.apple.backupd[7853] Could not resize backup disk image (DIHLResizeImage returned 22) 1/4/12 8:34:14 PM com.apple.backupd[7853] QUICKCHECK ONLY; FILESYSTEM CLEAN 1/4/12 8:34:15 PM fseventsd[38] could not open <</Volumes/Time Machine Backups/.fseventsd/fseventsd-uuid>> (No such file or directory) 1/4/12 8:34:15 PM fseventsd[38] failed to store the uuid in /Volumes/Time Machine Backups/.fseventsd/fseventsd-uuid. unlinking it. 1/4/12 8:34:15 PM mds[32] (Normal) DiskStore: Creating index for /Volumes/Time Machine Backups/Backups.backupdb 1/4/12 8:34:16 PM com.apple.backupd[7853] Disk image /Volumes/ReadyNAS/my.sparsebundle mounted at: /Volumes/Time Machine Backups 1/4/12 8:34:16 PM com.apple.backupd[7853] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb 1/4/12 8:34:16 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:16 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:16 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:19 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:19 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:19 PM com.apple.backupd[7853] Exception writing exclusions cache. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:19 PM com.apple.backupd[7853] Unable to create exclusions cache data. 1/4/12 8:34:19 PM com.apple.backupd[7853] Failed to write exclusions cache. Continuing anyway. 1/4/12 8:34:19 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:19 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:19 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:30 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:30 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:30 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:30 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:30 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:30 PM com.apple.backupd[7853] Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device 1/4/12 8:34:30 PM com.apple.backupd[7853] Backup canceled. 1/4/12 8:34:30 PM fseventsd[38] disk logger: gzclose() failed (-1/28) removing all old log files in /Volumes/Time Machine Backups/.fseventsd 1/4/12 8:34:30 PM fseventsd[38] failed to store the uuid in /Volumes/Time Machine Backups/.fseventsd/fseventsd-uuid. unlinking it. 1/4/12 8:34:31 PM com.apple.backupd[7853] Ejected Time Machine disk image.

Opening the sparsebundle with diskutil shows ~170GB available.

Huh? What do I have to do to get the timemachine bundles copied over from the old NV+s to the new Pro ... and working?

What versions of RAIDiator are on the two devices?

What version of Mac OS X are you running?

Pro == 4.2.19
NV+ == 4.1.8
Mac == 10.6.8

Did you a TM backup on the NV+ after updating to 4.1.8?