NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Backup & restore iscsi_lun_backing_store on RNDU2000
Hello guys,
I need to wipe all data from my drives + do a factory reset and I'm wondering if I can just copy the iscsi_lun_backing_store file and restore it after wiping.
Do I have to configure the new LUN same way it was configured earlier (name, size, etc)?
What's more, I'd like to copy all my config files same way (like /my_volume/._share, /my_volume/.apps and parts of /etc). Will my apps (I care mainly about OwnCloud) and system config (shares) work as expected after that?
Just to note: my unit is running RNOS 6.5.1 - Tech support mode ATM.
I finally got some time to make it work.
Regarding main topic, just for the record: like kohdee said, exact LUN config is needed. Then it's enough to just copy iscsi_lun_backing_store and .serial_number. After this operation i've noticed that the free space diminished twice the size of my LUN. Unassigning the LUN and assigning it back to a group did the trick.
As for the other data, it wasn't so straightforward. In my case, despite the fact my backed up readynasd database file was quite large, for some reason, selecting data from any of its tables returned zero rows.
Copying my old ._share/ and /etc/frontview/*/Shares.conf did not work either. They were overwritten by defaults on each reboot - even after inserting proper data into db.
I wasn't up for creating btrfs subvolumes (thx kohdee for the info, I wouldn't come up with that) manually, so I had to create all the shares from frontview and then do update/insert on db.
8 Replies
Replies have been turned off for this discussion
Hi firerain,
I am not really very familiar with ISCSI. Let me inquire about your case first.
Regards,
If you're trying to restore a LUN, create a new LUN exactly the same, then overwrite it with the iscsi_lun_backing_store and the .serialnumber file that is also in the system. Some initiators would not mount correctly if the serialnumber file is not there. There's no need to make changes to the ._share if you create the LUN before then overwrite.
Thx kohdee.
I'm not sure if I remember the exact LUN configuration. I just got second RNDU2000, I'll upgrade it to same RNOS and try copying LUN.
About the other files I've mentioned (like ._share): just wanted to get back my configuration as I don't have any recent config backup.
I'll rebuild dir structure with ACLs and play a bit with copying over system files from old unit... and report back my findings here.
I'm not sure what settings you're concerned with losing by not copying the ._share folder. There isn't much config there except snapshot configuration and maybe the iSCSI LUN comment.
Settings like shares configuration (SMB valid users, NFS and AFP config, etc) but I assume it will work after copying.
Most important for me is whole OwnCloud config which should work too, at least I hope it will :smileywink:
Oh, I see. You're also inquiring about copying over share configs.
On boot, we mount any applicable data volume then we scan /*/._share/ and look for the configs. Then the configs are added to the middleware database and distributed to their appropriate places (like SMB config). Keep in mind that "shares" are actually btrfs subvolumes , so if you're copying data through the backend, don't just create a folder in the main btrfs volume.
Apps are actually stored in /apps or /data/.apps, and their configs are all stored there. The settings should be the same if you copy the whole .apps folder over between units.
Oh, I see. You're also inquiring about copying over share configs.
Yea, sorry for not being clear enough about that.
On boot, we mount any applicable data volume then we scan /*/._share/ and look for the configs. Then the configs are added to the middleware database and distributed to their appropriate places (like SMB config). Keep in mind that "shares" are actually btrfs subvolumes , so if you're copying data through the backend, don't just create a folder in the main btrfs volume.
So it works as it should :smileyhappy:
Thank you very much for the prompt reply.
I finally got some time to make it work.
Regarding main topic, just for the record: like kohdee said, exact LUN config is needed. Then it's enough to just copy iscsi_lun_backing_store and .serial_number. After this operation i've noticed that the free space diminished twice the size of my LUN. Unassigning the LUN and assigning it back to a group did the trick.
As for the other data, it wasn't so straightforward. In my case, despite the fact my backed up readynasd database file was quite large, for some reason, selecting data from any of its tables returned zero rows.
Copying my old ._share/ and /etc/frontview/*/Shares.conf did not work either. They were overwritten by defaults on each reboot - even after inserting proper data into db.
I wasn't up for creating btrfs subvolumes (thx kohdee for the info, I wouldn't come up with that) manually, so I had to create all the shares from frontview and then do update/insert on db.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
