This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
We have a RN312 in RAID1 configuration which we use for sharing some folders and also for providing iSCSI drives to a couple of Windows machines. We are thinking of buying another RN312 chassis (with no drives) as a replacement, just in case the power supply of the main RN312 gets burned.
The question is:
Is there any way to move the drives from a supposed faulty unit to the replacement chassis and have the new unit to recognize the LUNs for iSCSI? I mean, I have seen that I can backup RN configuration to a USB (and that will copy things as users, shares, IP, etc.) but will that copy LUNs and iSCSI associations as well? and what about RAID configuration?
If not, can you think of any way to do this in order to be able to move the drives from one faulty chassis to another empty one the more transparent way and with minimum re-configuration of the new unit?
All your data including your configuration is on the disks so it will remain when moving the disks to another chassis. If the only problem is hardware failure then this should work fine.
However sometimes users mistake an issue on the disks for hardware failure or have both hardware failure and another issue. If there is an issue on the disks it will remain when moving the disks to another chassis.
You should regularly backup your data e.g. using software on the PC the iSCSI initiator is running on.
All your data including your configuration is on the disks so it will remain when moving the disks to another chassis. If the only problem is hardware failure then this should work fine.
However sometimes users mistake an issue on the disks for hardware failure or have both hardware failure and another issue. If there is an issue on the disks it will remain when moving the disks to another chassis.
You should regularly backup your data e.g. using software on the PC the iSCSI initiator is running on.
Is the firmware also in the drives? Just having one exact model RN31200 as replacement would be enough, or will it have to be a specific release or firmware version?
The OS runs from a boot partition on the drives. but it is also in the flash. With OS6, when you migrate disks the boot process compares the flash version with the on-disk version. If there is a mismatch, than it takes whatever if newer. That is, if the flash is newer. the flash version is installed to the disks. If the boot partition is newer, the flash is updated from the boot partition.
There is also code in there to support ARM->x86 and X64->ARM migration, which is pretty cool.
So you don't need to precisely match the model or the firmware in it's flash.
Still, I do suggest installing a temporary scratch disk in the new unit first, and update the firmware first if that is necessary. Then power down and do the disk migration. Perhaps that is overly cautious, but I'd rather not risk a failed firmware update when I'm migrating. Plus it does provide some assurance that the replacement chassis is working properly.
Can you let me know what firmware is running in both the pro-2 and the pro-4?
The best thing to do now is to create the shares you want on the pro-4, and then use a frontview backup job to copy the files in those shares over from the pro-2. Rsync is a good backup mechanism for this. Create one backup job for each share (letting it finish before starting the next).
Specify what you want to backup. The path you want to backup can be in a share on this device (a USB disk attached to this device will show up as a share) or located remotely. The backup source and destination cannot both be remote shares.
“Share: archived”
Host: “Grey – Unable to add info”
Path: “HALL-NAS” Browse “Grey – Shows me Archive”
Login: “Grey – Unable to add info” Password: “Grey – Unable to add info”
Test connection “Grey – Unable to test”
STEP 2 - Select backup destination
Specify where you want your backup data saved. As with the backup source, the destination path can be a share on this device or a path on a remote PC or device.
“Share: archived”
Host: “Grey – Unable to add info”
Path: “HALL-NAS4” Browse “Grey – Shows me Archive”
Login: “Grey – Unable to add info” Password: “Grey – Unable to add info”
Create a backup job for each share on the PRO-4 that copies the data directly from the same share on the Pro-2. Enable Rsync for the shares on both NAS first.
Here's an example assuming that the source NAS has IP address 10.0.0.15 for a share called "backup". I'm showing all the settings needed to set this up to run every day, though you can of course just run it once.
Thsmks for the additional information. Sorry that I am so dense,
Because I don't see any specific reference to the NAS-4, I assume that you are running FrontView on the destination NAS4. ie: This is a "PULL" operation.
Correct?
Question, how did you get screen shots in the reply? What programs are you using? Thanks again!
Because I don't see any specific reference to the NAS-4, I assume that you are running FrontView on the destination NAS4. ie: This is a "PULL" operation.
Yes. The pro-6 actually backs up my RN526 - but the same backup settings will work between your pro-2 and your pro-4.
Question, how did you get screen shots in the reply?
Actually I just use built-in windows tools. I copy the window with alt-PrtSC, then I paste it into paint with a ctrl-v. I then crop it, and save it as a png. There is an image tool in the posting tool bar the lets you insert the pngs into the post.
I found the "rsync column" that needed me to set the "rights" to "read/write" for my backup job. Once I had all of them "Checkmarked", the "Test Connection" worked and my "Test Backup" also worked.
Hopefully, tomorrow morning will show me a "Completed" message on my "Share of Acronis Archived Backups"! Then I have 6 more to do, 1 each night.
Looks like all 6 shares of the Pro 2 copied ok to the Pro 4. But it apparently didn't copy the Photo II photos. I added the Photo II app to the Pro 4 before doing the Rsync from the Pro 2 drives.
When I do a Windows Explorer on the Pro 2, I find, in addition to the 6 shares, file folders named "admin", "c" containing folder ".RNP2", & "home".
In reading various forum subjects about Photo II, I found one talking about treating "/c/.RNP2" as a share like I did for the previous 6 shares.
It also stated that the user should "add" the Photo II app "after" the Rsync for "/c/.RNP2" has completed and the Photo II app would automatically "sync" all of the photos in the albums. Is that true? If so, do I have to "uninstall" the Photo II app on the Pro 4 before doing the Rsync followed by "reinstalling" the Photo II app?
