NET701 Netapp Lab - part 2
Exercise 9
The goal of this exercise is to set up SAN storage using the iSCSI protocol.
Task 1
In this task, I had to allow the iSCSI protocol to be used on svm1.
I checked the iSCSI box and saved. Easy task.
Task 2
Next I needed to create a LIF. This is also easy to do with the OnCommand interface
here's a screenshot of the output of the create interface wizard.
Task 3
This was a quick task where I had to enable the iSCSI service. It's literally just a matter of clicking a button labelled 'Start'.
Task 4
For this task I created a SAN volume. here's the wizard input parameters.
I then had to change the security style from UNIX to NTFS
Task 5
Next was configuring SnapDrive so I could connect to the iSCSI drive.
It seemed like a very straightforward process, but I ended up having the following error.
A google suggested that it was to do with the version of SnapDrive, but I figured I would let it sit and come back to it later to see what I could do after finishing the first part of the lab. Surprisingly, after coming back I found that it was working as intended, so I could continue with the lab. This is similar to what happened with part 1 when I couldn't connect to the cluster. I suspect there is some instabilities with the lab environment, so giving it time often fixes it.
Task 6
For this task I just had to establish an iSCSI session.
Task 7
This task involved creating a LUN on svm1 using SnapDrive. This was completed quickly.
A google suggested that it was to do with the version of SnapDrive, but I figured I would let it sit and come back to it later to see what I could do after finishing the first part of the lab. Surprisingly, after coming back I found that it was working as intended, so I could continue with the lab. This is similar to what happened with part 1 when I couldn't connect to the cluster. I suspect there is some instabilities with the lab environment, so giving it time often fixes it.
Task 6
For this task I just had to establish an iSCSI session.
Task 7
This task involved creating a LUN on svm1 using SnapDrive. This was completed quickly.
Exercise 10
Again I started to have troubles with the lab environment. This time it was simply not connecting at all. I decided to just give it time again to see if it would work later.
I managed to load it up later, but I was reset so I unfortunately had to do Exercise 9 again.
Ugh I got the error I was having before in task 5 of exercise 9 as I was redoing it. Looks like I'll have to wait for it again like I did last time.
(Same as this)
Unfortunately I couldn't seem to get it working even after restarting the SVM, reopening the part 1 lab (This seems to reset the part 2 lab), and redoing settings in the OnCommand interface. I decided to just move on because this issue doesn't affect any of the other exercises and I had already done exercise 9 before.
This exercise covers ONTAP Snapshots and FlexClone clones
Task 1
For this task I had to create a Snapshot copy with the CLI. Using the CLI is very quick and I also noticed that the command modifiers like '-volume' can also be shortened to the smallest that it is unique. THis feature is not limited to general commands.
Task 2
This task followed on from the first one, I had to create a Snapshot copy using OnCommand instead.
Task 3
This task covered configuring Snapshots. The settings allow for different allocation of storage to Snapshots in percentage, and other stuff like time scheduling for Snapshots.
I also had to check the 'Show Snapshots' box as shown below.
Task 4
For this task, I deleted a folder that belongs to a snapshotted volume.
As we can see in this screenshot, the deleted folder can be recovered from the snapshot I made earlier.
Task 5
This task looked at how you can revert an entire volume to a snapshot.
Task 6
Thies task demonstrates that when you make a clone of a volume, the data is separated, so if you write to one vol it only writes to that vol.
I managed to load it up later, but I was reset so I unfortunately had to do Exercise 9 again.
Ugh I got the error I was having before in task 5 of exercise 9 as I was redoing it. Looks like I'll have to wait for it again like I did last time.
(Same as this)
Unfortunately I couldn't seem to get it working even after restarting the SVM, reopening the part 1 lab (This seems to reset the part 2 lab), and redoing settings in the OnCommand interface. I decided to just move on because this issue doesn't affect any of the other exercises and I had already done exercise 9 before.
This exercise covers ONTAP Snapshots and FlexClone clones
Task 1
For this task I had to create a Snapshot copy with the CLI. Using the CLI is very quick and I also noticed that the command modifiers like '-volume' can also be shortened to the smallest that it is unique. THis feature is not limited to general commands.
Task 2
This task followed on from the first one, I had to create a Snapshot copy using OnCommand instead.
Task 3
This task covered configuring Snapshots. The settings allow for different allocation of storage to Snapshots in percentage, and other stuff like time scheduling for Snapshots.
I also had to check the 'Show Snapshots' box as shown below.
Task 4
For this task, I deleted a folder that belongs to a snapshotted volume.
As we can see in this screenshot, the deleted folder can be recovered from the snapshot I made earlier.
Task 5
This task looked at how you can revert an entire volume to a snapshot.
Task 6
Thies task demonstrates that when you make a clone of a volume, the data is separated, so if you write to one vol it only writes to that vol.
Exercise 11
In this exercise, I had to set up deduplication. This feature is useful because in scenarios where many VMs and/or their applications are the same or similar, instead of fully storing everything, data that is the same can be stored once. Deduplication stores the data once and the different places it is used in all reference to the same place in the storage. This can result in massive storage savings.
Task 1
Task 3
Task 4
As we can see here with two exact copies of the same data, deduplication saves 50% in storage because the data only has to be stored once but referenced twice.
Task 3
Task 4
As we can see here with two exact copies of the same data, deduplication saves 50% in storage because the data only has to be stored once but referenced twice.
Exercise 12
This exercise covered how to change what aggregates can be used to hold volumes on a particular SVM.
Task 1
Task 2
Task 2
Conclusion
Looking back, the most amount of time on these labs was spent thinking about when to screenshot, saving screenshots in an organised way, getting them into the blog, and writing the blog.
Doing blogs is something I personally find unproductive because I find it difficult to focus on multiple things at once. The labs themselves are easy, but trying to organise all the blog stuff makes it much harder mentally. It will be interesting to see how I cope with future blogs.
Comments
Post a Comment