A bit distraught/discouraged. Need some suggestion and help

lazybummm

n00b
Joined
Apr 30, 2012
Messages
21
In a previous thread, I described some issues with a new OI/NAPP-IT that I've been slowly working through. I've spent quite a few hours trying to configure the server and have had limited success. The server and shares are up and running (install was generally easy as the guides were decent). However the permissions thing is killing me a bit, running into all kinds of road blocks on ACL.

What really scares me more is that I have no clue what happens when a disaster happens say when a storage drive dies or the drive the OS is on dies. The manuals I've read don't describe disaster events, I want to be confident that I can manage it because it is important data after all. I do plan to test disaster, but I just don't know how much more time I need to put in to figure out the ACL and disaster preparedness testing.

Anyway I wanted to get people's opinions on whether I should give up on this system and perhaps go to FreeNAS, it seems easier to administer and manage? But I understand OI/Napp-IT will have much better performance. I am also a bit undecided because I spent a bunch of money (close to $500) and a lot of time to source parts, including x6 1045t, Asus mobo that supports ecc, vt-d, (took a couple of tries, to get the right mobo) and 16gb of ecc ram, HBA (M1015); all that to run freenas seems a overkill. I have a HP Proliant N40L I bought for $140 I can run 6 drives and would be sufficient for FreeNAS. The drives can be easily transferred so I won't consider that cost.

Any thoughts would be greatly appreciated.
 
Disaster recovery normally refers to the process of restoring your system(s) from backup...it doesn't really become an issue until you have interdependent systems (ex: need gateway to get data to NAS from internet, need NAS to reinstall gateway) or are attempting to restore to dissimilar hardware in a hurry.

Since most people are using OI as a standalone storage server, recovering from OS drive failure is mostly a matter of reinstalling the OS on a new drive. Using vt-d over esxi does seem like an unnecessary complexity to me.

If the permissions thing really bothers you, you can always just pay for a nappit license.
 
Last edited:
I fought ACL quite a bit my self. My biggest problem was that I had a capital in my windows username and a lower case in Solaris. I not using AD.

Basically, follow the direction for the root piece then create the user in Napp-it. Then assign it to a group. Now connect to the share as root and then properties and security and add your user or group to permissions. Now I may be wrong on this, but you cannot set different permission sub folders. It really was that easy once I figured out the username issue.

Storage drive is trivial also. While playing around, I built my server in Vmware made a pool and decided I didn't want to use vmware. I wiped the vmware disk and installed my os back and then imported the pool. The only time spender here was setting up permissions again. Look for the zfs import command


Your little HP would be sufficient to do file serving for either os with some tweaking. You need to compare the differences in pool versions and if you need the additional features that solaris has.
 
I fought ACL quite a bit my self. My biggest problem was that I had a capital in my windows username and a lower case in Solaris. I not using AD.

Basically, follow the direction for the root piece then create the user in Napp-it. Then assign it to a group. Now connect to the share as root and then properties and security and add your user or group to permissions. Now I may be wrong on this, but you cannot set different permission sub folders. It really was that easy once I figured out the username issue.

Storage drive is trivial also. While playing around, I built my server in Vmware made a pool and decided I didn't want to use vmware. I wiped the vmware disk and installed my os back and then imported the pool. The only time spender here was setting up permissions again. Look for the zfs import command


Your little HP would be sufficient to do file serving for either os with some tweaking. You need to compare the differences in pool versions and if you need the additional features that solaris has.

Interesting. I didn't have any problems with username logging in since the username and pw were the same on windows and Napp-it. But I am confused about logging in as root. If I put my username (same as the one on windows) in the administrator group, am I automatically logged on as root when my network folders show up?

Also which windows OS are you using to configure the permissions/security? Win7 ultimate supposedly has problems, so I setup a virtual XP Pro SP3 machine on the ESXi box to set the settings, but I don't see any security or sharing options when I go to the properties of the folders. I did do a little search, it maybe due to a "simple share" setting issue, I haven't had anytime to explore again since the weekend, do you know off top of your head?

Finally I still can't access napp-it web UI on my other computers on the network, only from OI. I check the settings on Napp-it and there are no IP access restrictions. When I try to load the Web UI from another computer, it gets stuck on "loading" web UI, I'm using FF, could that be the problem? But FF is also used on OI.
 
Last edited:
I don't think your user has "ownership" of the folders at this point. You need to log in as root because in the beginning root is the only user that has ownership of a folder. You don't need to mess with this either.

I think your windows security box is because your user doesn't have the permissions(see above), so why show a screen they cannot access.


I would check my java settings on the other computer??? Also make sure you are hitting port 81 for the ip. I really can't answer that one. Oh and I noticed on one of my browsers I had to include http. Oh and I normally access it by ip and not the servername. So maybe if you are using a server name you are having some dns issue.
 
Back
Top