Decibel1000
Dabbler
- Joined
- Nov 13, 2012
- Messages
- 16
Hello!
I have a box in my company running FreeNAS X64 8.3.1 with 4GB RAM, 1 Proc Core 2 duo, and 6 x 2TB Seagate Cosmopolitan drives on a RAID Z2 configuration. This is a very old installation and it holds several backups from our business. This is of course not the only backup server we rely on but it would be a mess to lose anything on it. This box has proven to be very reliable over the time. As SMART tests detects any small issue on any drive we replace that drive immediately with a new one and the resilver task is always trouble free. So this box actually works, data seems to be safe despite the slow processor and very low amount of memory. The problem is that this box is slow, data transfers are very slow as all data is compressed, so it's time to move to a new hardware.
For the new hardware we bought an Intel DBS1200SPS motherboard (originally it would be a SM, but we couldn't find a reliable distributor in Brazil), a quad core XEON processor 3.4GHz with HT (total 8 core) and 32GB ECC RAM.
With this hardware I thought in installing a fresh FreeNAS version v11, mount and import the disks from the old box, load the configuration backup and upgrad zpool for a while, and be happy, however doing several simulations on a virtual environment I found that this isn't as transparent as I though it would be, mainly on the integration with our AD.
On my tests I found that the AD integration is a bit different and this might be impacting on my tests. I couldn't make any previous shares available on the network because of no user had the permissions to access those shares. SMB is working, I can list the server and shares from a Windows station but can't access the data. I don't know if this is an AD integration issue or has to do with the differences between the two FreeNAS versions.
Any tips on how to make this work? I thought in start the configuration from scratch but there are too many shares and a complex permission scheme with several security groups assigned to each share and different permissions for each group, so this would make this migration too complex.
I really appreciate your thoughts and advice.
Thanks!
I have a box in my company running FreeNAS X64 8.3.1 with 4GB RAM, 1 Proc Core 2 duo, and 6 x 2TB Seagate Cosmopolitan drives on a RAID Z2 configuration. This is a very old installation and it holds several backups from our business. This is of course not the only backup server we rely on but it would be a mess to lose anything on it. This box has proven to be very reliable over the time. As SMART tests detects any small issue on any drive we replace that drive immediately with a new one and the resilver task is always trouble free. So this box actually works, data seems to be safe despite the slow processor and very low amount of memory. The problem is that this box is slow, data transfers are very slow as all data is compressed, so it's time to move to a new hardware.
For the new hardware we bought an Intel DBS1200SPS motherboard (originally it would be a SM, but we couldn't find a reliable distributor in Brazil), a quad core XEON processor 3.4GHz with HT (total 8 core) and 32GB ECC RAM.
With this hardware I thought in installing a fresh FreeNAS version v11, mount and import the disks from the old box, load the configuration backup and upgrad zpool for a while, and be happy, however doing several simulations on a virtual environment I found that this isn't as transparent as I though it would be, mainly on the integration with our AD.
On my tests I found that the AD integration is a bit different and this might be impacting on my tests. I couldn't make any previous shares available on the network because of no user had the permissions to access those shares. SMB is working, I can list the server and shares from a Windows station but can't access the data. I don't know if this is an AD integration issue or has to do with the differences between the two FreeNAS versions.
Any tips on how to make this work? I thought in start the configuration from scratch but there are too many shares and a complex permission scheme with several security groups assigned to each share and different permissions for each group, so this would make this migration too complex.
I really appreciate your thoughts and advice.
Thanks!
Last edited by a moderator: