@@@@ Official Storage (San/nas) @@@@@@

[Nippu tunaka]

[quote name='pawankalyan' timestamp='1362718600' post='1303384628']


Summarizing

ISCSI is less expensive when compared to FC

ISCSI is easy to implement, because it uses Ethernet cables.

When we use FC we have to create zones a logical relation between host and LUN. where as in ISCSI no zones were created.

ISCSI is more secure than FC.


Bhayya ikkada oka doubt. ISCSI ki chala advantages unnappudu real time lo ekkuva FC enduku vadutunnaru.
[/quote]

san pay rate pls

[girishv]

[quote name='pawankalyan' timestamp='1362718600' post='1303384628']



Summarizing

ISCSI is less expensive when compared to FC

ISCSI is easy to implement, because it uses Ethernet cables.

When we use FC we have to create zones a logical relation between host and LUN. where as in ISCSI no zones were created.

ISCSI is more secure than FC.


Bhayya ikkada oka doubt. ISCSI ki chala advantages unnappudu real time lo ekkuva FC enduku vadutunnaru.
[/quote]

Office lo no DB....e link lo baga explain chesthadu...doubts unte evening cheptha...

searchvirtualstorage.techtarget.com/news/2240148541/Virtual-server-storage-Choosing-between-Fibre-Channel-iSCSI-and-NAS

[pawankalyan]

I am attending some netapp classes.These are the some of the points i found important in that tutorial. May be helpful for very beginners.




Summary:

Aggregate is the combination of raid groups with the same raid type.
raid group as limitation.
each raid group as maximum of 16 drives in raid type Raid 6.
each raid group as maximum of 8 drives in raid type Raid 4.
* Aggregate as no limit for number of drives
* There is no limit for number of raid groups in Aggregate.
*There is a limit for aggregate size.
But how we are getting the size limit.

In 7.3 version of ONTAp. we have 32 bit aggregates
In 8.0 version of ONTAP. we have both 32 and 64 bit aggregates. But default is 32 bit. The root agrregate is 32 bit.
In 8.1 version of ONTAP. We have 64 bit aggregate as default size.we can also have 32 bit.

* Lets Try to understand what is this 32 bit and 64 bit.
block size on Netapp = 4k bytes
disk block size is 512 bytes.

* In 32 bit we can have 2^32 adrreses and we can store 2*32*4k=16 TB
*In 64 bit we can have 2^64 addreses and we can store 2*64*4k=67 million PB.

* 8.0 version FAS2040 ----30TB (Max Size)
FAS6280 ----100TB(MAX SIZE)
*8,1 Version FAS2040----50TB
FAS6280----162TB

We can create a raid group with less than the default raid size.
the best practice is to have the raid groups with equal sizes in a aggregate to avoid performance issue.
We can expand aggregate by adding additional drives.but we cannot remove drive from the aggregate
Adding a drive doesn't have any performance issues.
For data integrity we have blocked checksum & zoned checksum(Netapp using Blocked Checksum)
Scrubbing is the thing used to check the error(bad blocks) in the disks. If we get more scrub errors it have a high propability of failure.we can find the scrub errors at /etc/messages.
In a raid group netapp supports the disks with different sizes. But the highest capacity drive should be a parity disk.
Netapp support FC and SAS drives existing within the same raid group since they have equal performance. we cannot intermix sata and saas or fc or sata.

* Two types of volumes exists:
---->Traditional volume.
---->Flex volume.

Flex volume:
* Will be create within the aggregate.
*Lowest volume size = 20MB.
*Highest Volume size = 30TB for FAS2040.
*There is a limit for number of volumes in filer.Varies from model to model.
*Single filer has limit in number of aggregates. Maximum 100 agrregates per filer.
*Agrregate should not have two volumes with same name.
* We can increse or decrease the size of volume.

Traditional volume:
*We cannot decrease the size of the volume.but we can increase the volume
*Maximum of 100 volumes can be created in an aggregate.
Questions:


* Why we are creating aggregate?



Commands:

*Creatingthe raid group: aggr create aggr1
*How many raid groups in aggregate: sysconfig -r (or) vol status -
*How to know the spare drives in aggregate: aggr status -s
*How to Get the broken or failed drives: aggr status -f
*To Free the spare disk spaces: disk zero spares
*Manually forcing the disk to fail: disk fail 0a.20 :so it will copy the data to new spare disk.
*To make our job easy while removing the right drive from disk shelf is
Run the following commands
priv set advanced
led off 0a.19
led off 0a.21
* To go back to admin mode: priv set admin
so now we can identify our failing disk easily to remove.
*To replace a disk manually with another disk: disk replace 0a.19 0a.21
* To delete all the data in the disk if we are selling this disks: disk sanitize 0a.19 : We should have license to run this command.
* To read the scrub errors: rdfile /etc/messages.
* To read the log files: rdfile /etc/log/auditlog
* Creating volume : vol create vol1 aggr1 100m
* Changing sizes : vol size vol1 +50m ----150m
* To increase the volume size automatically: vol autosize -i 100m -m 500m on (This will increase 100m each time and increses upto 500m)
* To create a traditiona volume : vol create tradvol1 24
* To add disks to traditional volume: vol add tradvol1 12

[pawankalyan]

I have some doubt regarding the maximum number of drives for each raid group.

I got to know that, there is no limit for that, but there should be some best practices from netapp. could anyone please help me with that.

[pawankalyan]

This is another class summary. may be helpful


Summary:

*All the variable changes using option are saved in /etc/registry.Never edit this file.
*RC file is runconfig file. Some of the config files have to store permenantely
*Default packeting size in networking is 1 by 1/2 size.enable jumbo files to increase the performance as file size increases acknowledgements decreases.
*In netapp it is difficult to edit the file, so the recommendation is do that from NFS or CIFS client.so use admin host as windows or unix.
* All the configuration files are in etc directory.
*To manage filer remotely we use Baseboard management control(BMC).To power on, to power off.
*press CTRL+G will go to the BMC shell
*SAS is a point to point interface but FC is arbitrated loop. so FC drives are going away.
*Role based access control(RBAC).


Commands:

*List of disks : sysconfig -d
*To know the incompatibilty B/W hardware and software : sysconfig -c
*List of tape drives : sysconfig -t
*List of raid groups : sysconfig -r

Important thing is options:

aggr options aggr1; vol options vol1

*To list all the sub options: options telnet
*To enable Telnet: options telnet.enable on
* To give telnet access to every one: options trusted.hosts *
* To give access to particular host: options telnet.access host=host1, 192.168.10.201
* To give access to no one: options telnet.access -
*options ssh
*To enable ssh:options ssh.enable on
*secureadmin setup ssh
*To shutdown the filer after 24 hours once the disk fails and no spare disk available : option raid.timeout 24
* To destroy aggregate.
First we have to destroy volumes in that aggregate
Take it to offline: vol offline vol2
vol destroy vol 2
Take aggregate offline: aggr offline aggr2
aggr destroy aggr2
*To show spare disks: aggr status -s
* Create aggregate : aggr create aggr3 -B 64 -t raid 4 2 (Here 2 represents number of disks)
* To check space available: df -Ag
* Create a LUN: lun create -t windows -s 100m /vol/vol11/wlun
* To automatically resize the volume: vol autosize vol11 -i 100m -m 500m on
*To increase the lun size: Lun resize /vol/vol11/wlun +80m
*Options: options autologout.console.timeout 5
* To see the user: rdfile /etc/passwd
*useradmin role
*To list group information: useradmin group list
* create user: useradmin user add uni678 -g administrator

[pawankalyan]

[quote name='Nippu tunaka' timestamp='1362759099' post='1303386834']

san pay rate pls
[/quote]


my employer will quote around $55 to $70 dollars. depending on our experience.

[saisankart]

Guys, I am an Oracle DBA. But, would like to change my career route to SAN. Please let me know who can give the best training....

[girishv]

[quote name='pawankalyan' timestamp='1362871122' post='1303395182']
I have some doubt regarding the maximum number of drives for each raid group.

I got to know that, there is no limit for that, but there should be some best practices from netapp. could anyone please help me with that.
[/quote]


neeku NOW account unda? unte oka link istha....chala info undi..lekapothe ikkade paste chestha....

[girishv]

Some thoughts on your class 1:

Don't worry too much about traditional volumes...ivala repu evaru use cheyaru...they can grow...shrink avvavu...so no one is using them...traditional volumes ante ento thelusukunte chalu....

manam aggr. create chestham disks nunchi...we don't create raid groups...

layman language lo cheppali ante...aggr. ni bucket anuko...volumes ni mug anuko...evaranna water kavali ante bucket isthava? mug isthava? aggr. is a logical space created from disks...adhi direct ga storage provision ki use cheyalemu, we need to create volumes and qtrees...

priv set advanced mode use cheyadu...specially freshers...chala dangerous commands untayi...only case open chesina time lo netapp
support vallu chepthe use cheyandi....priv set advanced nunchi admin mode ki ravali ante..[b].priv set admin[/b] or just [b]priv set[/b] ani ichina chalu...

[Nippu tunaka]

[quote name='30 yrs industry' timestamp='1362937027' post='1303399150']


neeku NOW account unda? unte oka link istha....chala info undi..lekapothe ikkade paste chestha....
[/quote]

paste it here pls

[Nippu tunaka]

[quote name='indiaprince' timestamp='1362883410' post='1303395691']
Guys, I am an Oracle DBA. But, would like to change my career route to SAN. Please let me know who can give the best place for training....
[/quote]

Babai oracle apps dba ki baagane vundiga? enduku change avvalanukuntunnav? nenu oracle apps dba ki move avudaamanukuntunna? whats your suggestion?

[girishv]

[quote name='Nippu tunaka' timestamp='1362947817' post='1303400341']
paste it here pls
[/quote]


[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]There has been a lot of work put into aggregate and RG sizing recommendations at NetApp. The documents that cover this information are currently NDA --- if you are covered by an NDA with NetApp you can request these documents from your account team (reference TR3838, the Storage Subsystem Configuration Guide or the Storage Subsystem Technical FAQ --- both cover the RAID group sizing policy). For those who are not covered by NDA with NetApp --- since the RG sizing policy itself is not confidential I will paste the text below (from the FAQ --- hence the question/answer format). This is the official NetApp position on RG sizing.[/size][/font][/color]

[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3][b]<policy>[/b][/size][/font][/color]
[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3][b]SHOULD ALL AGGREGATES ALWAYS USE THE DEFAULT RAID GROUP SIZE?[/b][/size][/font][/color]
[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]The previous approach to RAID group and aggregate sizing was to use the default RAID group size. This no longer applies, because the breadth of storage configurations being addressed by NetApp products is more comprehensive than when the original sizing approach was determined. Sizing was also not such a big problem with only 32-bit aggregates, which are limited to 16TB. You can fit only so many drives and RAID groups into 16TB. The introduction of 64-bit aggregates delivers the capability for aggregates to contain a great number of drives and many more RAID groups than was possible before. This compounds the opportunity for future expansion as new versions of Data ONTAP[sup]®[/sup] support larger and larger aggregates.[/size][/font][/color]

[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]Aggregates do a very good job of masking the traditional performance implications that are associated with RAID group size. The primary point of this policy is not bound to performance concerns but rather to establishing a consistent approach to aggregate and RAID group sizing that:[/size][/font][/color][list]
[*]Facilitates ease of aggregate and RAID group expansion
[*]Establishes consistency across the RAID groups in the aggregate
[*]Reduces parity tax to help maximize “usable” storage
[*]Reduces CPU overhead associated with implementing additional RAID groups that might not be necessary
[*]Considers both the time it takes to complete corrective actions and how that relates to actual reliability data available for the drives
[/list]
[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]These recommendations apply to aggregate and RAID group sizing for RAID-DP[sup]®[/sup]. RAID-DP is the recommended RAID type to use for all NetApp storage configurations. In Data ONTAP 8.0.1, the maximum SATA RAID group size for RAID-DP has increased from 16 to 20.[/size][/font][/color]

[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]For HDD (SATA, FC, and SAS) the recommended sizing approach is to establish a RAID group size that is within the range of 12 (10+2) to 20 (18+2); that achieves an even RAID group layout (all RAID groups contain the same number of drives). If multiple RAID group sizes achieve an even RAID group layout, NetApp recommends using the higher RAID group size value within the range. If drive deficiencies are unavoidable, as is sometimes the case, NetApp recommends that the aggregate should not be deficient by more than a number of drives equal to one less than the number of RAID groups. Otherwise you would just pick the next lowest RAID group size. Drive deficiencies should be distributed across RAID groups so that no single RAID group is deficient more than a single drive.[/size][/font][/color]

[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]Given the added reliability of SAS and Fibre Channel (FC) drives, it might sometimes be justified to use a RAID group size that is as large as 24 (22+2) if this aligns better with physical drive count and storage shelf layout.[/size][/font][/color]
[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]SSD is slightly different. The default RAID group size for SSD is 23 (21+2), and the maximum size is 28. For SSD aggregates and RAID groups, NetApp recommends using the largest RAID group size in the range of 20 (18+2) to 28 (26+2) that affords the most even RAID group layout, as with the HDD sizing approach.[/size][/font][/color]
[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3][b]</policy>[/b][/size][/font][/color]

[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]In addition to the policy, we publish tables for maximum size aggregates (which are also not confidential but are in the NDA docs):[/size][/font][/color]

[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3][b]<64-bit aggregates>[/b][/size][/font][/color]
[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3][b]HOW MANY DRIVES CAN BE USED IN A MAXIMUM SIZE 64-BIT AGGREGATE?[/b][/size][/font][/color]
[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]64-bit aggregates are supported with Data ONTAP 8.0 and later. Each platform has different maximum aggregate capacities for 64-bit aggregates. The following recommendations are based on attempting to provide the optimal RAID group layout, as explained in the answer to the question “Should all aggregates always use the default RAID group size?” earlier.[/size][/font][/color]

[color=#454545][font=Arial, Helvetica, Verdana, sans-serif][size=3]The column descriptions for the following tables are as follows:[/size][/font][/color][list]
[*]“Data Drives” is the number of data drives that fit within the maximum aggregate capacity (based on usable drive capacity).
[*]“RG Size” is the recommended RAID group size to use for the configuration.
[*]“Number of RGs” is the resulting number of RAID groups the aggregate will contain.
[*]“Drive Def.” is the number of drives deficient the configuration is from achieving event RAID group layout.
[*]“Data + Parity” is the total number of drives used for the aggregate configuration.
[/list]

[saisankart]

[quote name='Nippu tunaka' timestamp='1362947897' post='1303400344']

Babai oracle apps dba ki baagane vundiga? enduku change avvalanukuntunnav? nenu oracle apps dba ki move avudaamanukuntunna? whats your suggestion?
[/quote]


Nenu Oracle Core DBA. Prasthutham full time lo unna. Within the company verey technology nerchukotaaniki/change avvataaniki opportunities baaga untaayi. So, want to learn.

[saisankart]

Guys, SAN ki training iche manchi contact details fwd cheyyandi please!!!!!!!!!!!!!!!!!

[dude_dude]

[quote name='indiaprince' timestamp='1363095010' post='1303408490']
Guys, SAN ki training iche manchi contact details fwd cheyyandi please!!!!!!!!!!!!!!!!!
[/quote]

Message me your details.