Subscribe
Accepted Solution

New install FAS2020

Hello, i'm french, sorry for my bad english !

I receive a FAS2020 with 12 SAS 450go and 2 controller.

I have some question :

-controller 1 assign 4 disk,(1 spare and 3 for root aggr0)

-controller 2 assign 8 disk (5 spare and 3 for root aggr0)

its a probleme for me !

they are 6 disk used for root ???

if i want used more space, how to do this ???

Re: New install FAS2020

It is a best practice to keep root on a separate aggregate (wafl_check , wafliron), however on smaller systems like this we often use one aggregate to contain all volumes.  Just make sure you have a volume guarantee on all volumes (default is volume guarantee)  so the root volume never runs out of space.  So you could do something like below to get about 2TB usable across both nodes (6x 450GB data drives split across 2 controllers)..

controller1

   1x  spare

   3x  aggr0  (rg0: 1D+2P)

controller2

   1x spare

   7x aggr0   (rg0: 5D+2P)

Or you could make a more even layout to use both nodes symmetrically (not required) to get ~1TB usable per node.

controller1

   1x  spare

   5x  aggr0  (rg0: 3D+2P)

controller2

   1x spare

   5x aggr0   (rg0: 3D+2P)

Re: New install FAS2020

yes, if is it :

controller1

   1x  spare

   3x  aggr0  (rg0: 1D+2P)

controller2

   1x spare

   7x aggr0   (rg0: 5D+2P)

-on controller1it's possible to delete spare and affect it to controller 2 ? but if in controller 1 there are only root, why this ?

-it's not possible to delete root on controler 1 and if controler 2 is brake, controler 1 relay ?

I think with 2 root I lost very memory !

Re: New install FAS2020

Spares are not global, so each controller needs a dedicated spare.  Disk ownership is used to assign disks between controllers.  The layout below is for aggregates, not for root.  The root volume will be a flexible volume and can share aggr0 with other volumes.  For a larger system we don't prefer doing this, but for smaller systems like this it is common.  The root volume in aggr0 can be as small as 10GB for a 2020, but I wouldn't go that small...maybe 50 or 100GB or whatever is enough depending on if you are running cifs auditing or other logging.  Out of the 2TB, you will subtract the root volume size then have the rest of the aggr0 aggregate free for other flexible volumes.

Re: New install FAS2020

ok, thus,

in controller 1

3 disk + 1 spare for root,

vol0 : root total capacity (i didnt use 350go only)

in controller 2

7disk + 1 spare

vol0 aggr0 : root reduce to 50go

vol1 aggr0: for ESX, rest of capacity ???

it ok for this ???

-if a buy later extension disk, i could move root (controler 2)to a futur aggr1 ???

-as I asked, it's not possible to delete root on controller 1 ? and use controler 1 for spare ? not in cluster ? (active/passive)

Re: New install FAS2020

You always need a root volume on a controller - even if there is nothing else on it.

Basically you can move the root volume around. So potentially you may squeeze few extra gigabytes:

- create new aggregate containing 2 disk in RAID-4 (not DP)

- move the root volume from 3-disk aggregate to 2-disk aggregate

- destroy old 3-disk aggregate & assign disks to the other controller

- stick to one hot-spare per controller

Regards,
Radek

Re: New install FAS2020

Yes I see !

-for Raid 4, only 2 disk ? not 3 ? not spare ?

-what is the interest of active/active controller ?since it is independent

Re: New install FAS2020

Hi,

Andrew's response in http://communities.netapp.com/message/6776#6776  should help you a bit about the design.

Thanks

Daniel

Re: New install FAS2020

On controller 1 I change aggr0 on RAID 4 !

2disk + 1 spare, Spare is util ?

on controller 2 I think I do the same, ok ?

RAID 4 with 2 disk is suffisant for root ?

Re: New install FAS2020

You don't need a dedicated root aggregate - it may be recommended for bigger systems, but makes no sense with just 12 drives.

So you can assign 3 drives to controller 1 - assuming it will be in fact passive (containing only root volume), and all remaining drives to controller 2 - keeping there its root volume plus all your actual data (in separate volumes, but within the same aggregate)

Regards,
Radek