NetApp Volume - Revision history

Madsushi: /* Adjusting settings */

2011-10-30T08:58:37Z

‎Adjusting settings

Madsushi: /* Adjusting settings */

2011-10-30T08:57:09Z

‎Adjusting settings

Madsushi: /* Adjusting settings */

2011-10-30T08:56:12Z

‎Adjusting settings

Madsushi at 08:54, 30 October 2011

2011-10-30T08:54:21Z

Madsushi at 08:54, 30 October 2011

2011-10-30T08:54:07Z

Madsushi at 08:53, 30 October 2011

2011-10-30T08:53:55Z

Madsushi: /* Making a volume */

2011-10-30T08:53:36Z

‎Making a volume

Madsushi at 08:52, 30 October 2011

2011-10-30T08:52:16Z

Madsushi at 08:49, 30 October 2011

2011-10-30T08:49:19Z

Madsushi at 08:49, 30 October 2011

2011-10-30T08:49:09Z

@@ Line 66: / Line 66: @@
 [[File:Configdedupe.jpg]]
-Scheduled your dedupe jobs to happen before your snapshots happen. As an example, run dedupe at 10pm and then run your backups at midnight.
+Scheduled your dedupe jobs to happen before your snapshots happen. As an example, run dedupe at 10pm and then run your backups at midnight. The only exceptions to this rule are snapvault volumes, which are set to manual, since they automatically dedupe themselves. Automatic is always a bad idea.
 [[File:advvolume.jpg]]
-You can set up Autogrow, which will grow the volume if it fills up. Only use this for emergencies. You can also set it to Auto-delete older snapshots when it fills up, which is usually the better choice. Fractional Reserve needs to be on for every volume, no exceptions. Unless the volume is constantly managed by an expert, turning Fractional Reserve off is asking for serious trouble.
+You can set up Autogrow, which will grow the volume automatically if it fills up. Only use this for emergencies or very critical volumes. You can also set up Auto-delete to delete older snapshots when it fills up, which is usually the better choice for making sure you have free space. Finally, Fractional Reserve needs to be on for every volume, no exceptions. Unless the volume is constantly managed by an expert, turning Fractional Reserve off is asking for serious trouble.

← Older revision		Revision as of 08:57, 30 October 2011
Line 66:		Line 66:
	[[File:Configdedupe.jpg]]		[[File:Configdedupe.jpg]]

−	Scheduled your dedupe jobs to happen before your snapshots happen.	+	Scheduled your dedupe jobs to happen before your snapshots happen. As an example, run dedupe at 10pm and then run your backups at midnight.

@@ Line 55: / Line 55: @@
 == Adjusting settings ==
-Now that we've successfully created the volume, let's finish the setup.
+Now that we've successfully created the volume, let's finish the setup. You configure snapshots by selecting your volume, then going to the Snapshot Copies menu and hitting Configure.
 [[File:Snapsettings.jpg]]
@@ Line 61: / Line 61: @@
 Here's where you can make your snapshot directory visible (almost always good), enable scheduled snapshots, and configure when they're taken. If you're working with a volume that will be snapshotted by SnapManager for whatever, TURN OFF SCHEDULED SNAPSHOTS.
 [[File:Configdedupe.jpg]]

← Older revision		Revision as of 08:54, 30 October 2011
Line 23:		Line 23:

	* ''sv_PandoraSQL''		* ''sv_PandoraSQL''
		+

	== Making a volume ==		== Making a volume ==

@@ Line 15: / Line 15: @@
 For SQL or Exchange, you need 2-3 volumes. Use the volume name suffixed by SQL, Logs, or SnapInfo. If you're talking about Exchange or a non-SQL app, suffix the first volume with DB. For example:
-''PandoraSQL, PandoraLogs, PandoraSnapInfo''
+* ''PandoraSQL, PandoraLogs, PandoraSnapInfo''
-''ExchDB, ExchLogs''
+* ''ExchDB, ExchLogs''
 For SnapVaulted volumes, you add sv_ to the original volume's name. Example:
-''sv_PandoraSQL''
+* ''sv_PandoraSQL''
 == Making a volume ==

@@ Line 1: / Line 1: @@
 == What are Volumes? ==
@@ Line 51: / Line 50: @@
 * Compression is only used in very specific scenarios, '''ALWAYS LEAVE THIS OFF'''.
 == Adjusting settings ==

@@ Line 31: / Line 31: @@
 [[File:Volumenaming.jpg]]
-We already went over naming, you have that part handled.
+* We already went over naming, you have that part handled.
-You obviously want to pick the right aggregate, but for all non-CHS customers, this will always be aggr0.
+* You obviously want to pick the right aggregate, but for all non-CHS customers, this will always be aggr0.
-For Storage Type, the only thing that changes is whether it's exported by default or not. THIS CHOICE DOESN'T REALLY MATTER.
+* For Storage Type, the only thing that changes is whether it's exported by default or not. THIS CHOICE DOESN'T REALLY MATTER.
-Set your total size appropriately, but know you can move it up and down at will without any issues.
+* Set your total size appropriately, but know you can move it up and down at will without any issues.
-Snapshot Reserves will be covered in a later chapter, but '''ALWAYS SET THIS TO 0%'''.
+* Snapshot Reserves will be covered in a later chapter, but '''ALWAYS SET THIS TO 0%'''.
-Obviously turn off Thin Provisioning.
+* Obviously turn off Thin Provisioning.
@@ Line 48: / Line 48: @@
 [[File:Dedupesettings.jpg]]
-We'll turn on deduplication, obviously it's a good thing and should be turned on just about everywhere.
+* We'll turn on deduplication, obviously it's a good thing and should be turned on just about everywhere.
-−
-Compression is only used in very specific scenarios, '''ALWAYS LEAVE THIS OFF'''.
-−
 == Adjusting settings ==

@@ Line 1: / Line 1: @@
 == What are Volumes? ==
-The best way to think of a NetApp volume is to imagine a folder in Windows. All of the disk/RAID configuration is already taken care of at the aggregate level, and you're ready to start laying down some data. Rather than just throwing files around all over the place, you use Volumes (like folders) to sort your data. The big difference between a traditional folder and a volume is that a volume has a set size. Imagine if you went into a folder's properties and said "you can't be over 50 GB", that's what a volume is like. Not only do we say that the volume can't be over 50 GB, we actually fix its size at 50 GB. When you start talking about enterprise storage, you realize that you are able to thin-provision just about everything if you wanted to. '''NEVER THIN-PROVISION VOLUMES'''. Volumes should always be set to '''RESERVE''' their full space upon creation.
+The best way to think of a NetApp volume is to imagine a folder in Windows. All of the disk/RAID configuration is already taken care of at the aggregate level, and you're ready to start laying down some data.
-If you mess up volume thin-provisioning, you can take an '''entire aggregate''' down with you. If you mess up thin-provisioning inside of a volume, then only that volume is affected.
+If you mess up volume thin-provisioning, you can take an '''entire aggregate''' down with you. If you mess up thin-provisioning inside of a volume, then only that volume is affected. Speaking as a guy who has taken down plenty of volumes, don't mess this up.
 == Naming Volumes ==
@@ Line 9: / Line 12: @@
 Volume naming is something very dear to my heart. Please, standardize your volume names and realize that we will be using these volume names in conversation, so make them readable. Here are some CIO standards:
 For SQL or Exchange, you need 2-3 volumes. Use the volume name suffixed by SQL, Logs, or SnapInfo. If you're talking about Exchange or a non-SQL app, suffix the first volume with DB. For example: