We use deduplication on our N3600 (FAS2050C) with ESX (vSphere these days) via NFS.
I'm curious how those of you out there with a similar setup manage your disk space and identify "critical" threshholds. We also do thin provisioning so we're thinking about a worst-case scenario where we have to restore from backups and end up with thick provisioned and non deduped VMDK files.
We don't want to be too conservative though -- may as well not be using dedupe at all... :)
Interested in how others on the list deal with this.
Thanks, Ray
These should help:
http://media.netapp.com/documents/tr-3483.pdf http://media.netapp.com/documents/tr-3505.pdf
Good luck.
Cheers,
Stetson Webster Professional Services Consultant Virtualization and Consolidation NCIE-SAN, NCIE-B&R, SCSN-E, VCP
NetApp 919.250.0052 Direct Phone stetson@netapp.com Learn more: http://www.imaginevirtuallyanything.com
-----Original Message----- From: Ray Van Dolson [mailto:rvandolson@esri.com] Sent: Tuesday, July 27, 2010 7:48 PM To: toasters@mathworks.com Subject: Deduplication and space usage - best practices
We use deduplication on our N3600 (FAS2050C) with ESX (vSphere these days) via NFS.
I'm curious how those of you out there with a similar setup manage your disk space and identify "critical" threshholds. We also do thin provisioning so we're thinking about a worst-case scenario where we have to restore from backups and end up with thick provisioned and non deduped VMDK files.
We don't want to be too conservative though -- may as well not be using dedupe at all... :)
Interested in how others on the list deal with this.
Thanks, Ray
-
Ray Van Dolson -
Webster, Stetson