RE: Does anyone know if the dedup is across the entire aggr or just the volume in 7.3.x?
We're at vSphere, it does support 64 (and that's what the NetApp tool recommends). It's probably over ambitious to get one vol per service but maybe one per customer (Engineering, Finance etc). That should keep the similar data together. We too are seeing 40% or so on our VM's. It looks like Aggr level dedup will be out with 8.
________________________________
From: Glenn Walker [mailto:gwalker@aetas.org] Sent: Saturday, December 19, 2009 2:32 PM To: Page, Jeremy Cc: toasters@mathworks.com Subject: Re: Does anyone know if the dedup is across the entire aggr or just the volume in 7.3.x?
It isn't global dedupe, like Data Domain - I think that was one of the big benefits of the attempted purchase of DD.
That said, it's still pretty good - even if only at the volume level. We're seeing tremendous savings of storage and no real performance impact. We've got VMWare over NFS in our environment and on average we're seeing about 45% dedupe rates - pretty impressive given the fact that the application files, temp files, and page files are all co-termed on the same VMDKs. At last count, we've deduped 20TB of storage.
Keep in mind, volume per service may prove difficult as VMWare 3.5.X has a limit of 32 NFS-based datastores per server: if you run big clusters like we do, you'll probably run out of datastores if each volume is a separate service. VSphere is rumored to raise the limit to 64 I think.
Glenn
On Mon, Dec 7, 2009 at 1:39 PM, Page, Jeremy jeremy.page@gilbarco.com wrote:
Does anyone know if the dedup is across the entire aggr or just the volume in 7.3.x? I'd like to break up my VMware environment so we have a volume per service (so SQL Warehouse volume, Call Center etc). This would be nice because we could delegate the rights to them, move them around if specific apps required more IO and aid in troubleshooting. The question I have is will this kill our dedup percentages?
Please be advised that this email may contain confidential information. If you are not the intended recipient, please do not read, copy or re-transmit this email. If you have received this email in error, please notify us by email by replying to the sender and by telephone (call us collect at +1 202-828-0850) and delete this message and any attachments. Thank you in advance for your cooperation and assistance.
In addition, Danaher and its subsidiaries disclaim that the content of this email constitutes an offer to enter into, or the acceptance of, any contract or agreement or any amendment thereto; provided that the foregoing disclaimer does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment to this email.
Please be advised that this email may contain confidential information. If you are not the intended recipient, please do not read, copy or re-transmit this email. If you have received this email in error, please notify us by email by replying to the sender and by telephone (call us collect at +1 202-828-0850) and delete this message and any attachments. Thank you in advance for your cooperation and assistance.
In addition, Danaher and its subsidiaries disclaim that the content of this email constitutes an offer to enter into, or the acceptance of, any contract or agreement or any amendment thereto; provided that the foregoing disclaimer does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment to this email.
We had a bunch of NTFS LUN's on a server that crashed (2003x64/Snapdrive 4.2.1). We are trying to move the LUNS to another server(Snapdrive 6/Win2k3x64). To do this we did the following:
1) Unmap old initiator from lun
2) Zone new server to the Netapp filer.
3) Try to use connect disk from new server to the lun
4) This gives a error saying drive notification timeout
To debug this more, I opened Disk Management. The disks do not show up there either. But they show up as LUNs under Device manager. Why do the LUN's show up in Device Manager/Disk drives but not in Disk management?
Thanks
Suresh
Suresh Rajagopalan wrote:
We had a bunch of NTFS LUN's on a server that crashed (2003x64/Snapdrive 4.2.1). We are trying to move the LUNS to another server(Snapdrive 6/Win2k3x64). To do this we did the following:
Unmap old initiator from lun
Zone new server to the Netapp filer.
Try to use connect disk from new server to the lun
This gives a error saying drive notification timeout
what does lun show command show ?
does the new server have the user (that uses snapdrive to talk to the appliance) setup correctly ?
Hi all,
I'm going to do a swap of a 6030 cluster appliances with a 6040 ones. I've some doubt regarding LUN id and serials and disk ownership (6000 series perform the software ownership I know).
For which concern the LUNs both systems host a series of FC LUNs (Windows, VMware) and I remember (maybe wrong) that could be some issues on LUN serials changes and so on...is this correct?
The big concern regards the disk ownership. Times ago I've replaced a fault 3140 head on a cluster and once restarted I have had to reassign all the ownership to the disk yet pointing to the old sysid/name. I'm concerned that changing the head from 6030 to the new 6040 the disk ownership remain to the old 6030 and system will not start (missing mailbox disk and so on)...
There are some step to perform to be sure of successful hw upgrade?
Last: do you suggest me to upgrade to 7.3.2 (now is 7.2.x) before OR after the hw upgrade?
Thank you in advance
Hi Milazzo, I have performed a similiar upgrade from a 3050 cluster to a 3170 cluster. There are a lot more details to the upgrade than I've listed below but these are some big points that you'll need to cover.
1. Yes, the lun serials will change and you'll need to revert them back to the originals before you try to reconnect you clients. There are two scripts that I know of on the netapp communities page that help automate this. One for windows (vbs): http://communities.netapp.com/docs/DOC-1754 One for unix (or win too I guess, perl. I wrote this one): http://communities.netapp.com/docs/DOC-2369
2. You'll need to update your /etc/rc file ahead of time to deal with any network card name changes that may occur.
3. Yes, you'll need to reassign the disks to the new head. You do this in maintenance mode and with the "disk reassign" command.
4. You'll need to clear out the old mailboxes in maint mode also. mailbox destroy local mailbox destroy partner
5. You'll also want to make sure that your iscsi and fcp target nodenames are the same after the upgrade. You can do this with the "iscsi nodename" and "fcp nodename" commands.
6. You'll also want to make sure that the hardware model you are upgrading to uses the same version of OnTap that you are running on your current head, otherwise you'll need to upgrade that too.
If you'd like email me privately and I can get you a copy of my upgrade guide I used for my own upgrade.
Romeo
Following up on my post, we had HBA and path issues causing LUN corruption on several NTFS LUN's on the original host. As a result, we cannot even see a partition table on the LUN's.
Are there any utilities to manipulate or repair NTFS LUN files (which are visible as flat files via the CIFS share to the volume)?
Thanks
Suresh
From: Suresh Rajagopalan Sent: Tuesday, December 22, 2009 7:38 PM To: toasters@mathworks.com Subject: Cannot see LUNs after server move
We had a bunch of NTFS LUN's on a server that crashed (2003x64/Snapdrive 4.2.1). We are trying to move the LUNS to another server(Snapdrive 6/Win2k3x64). To do this we did the following:
1) Unmap old initiator from lun
2) Zone new server to the Netapp filer.
3) Try to use connect disk from new server to the lun
4) This gives a error saying drive notification timeout
To debug this more, I opened Disk Management. The disks do not show up there either. But they show up as LUNs under Device manager. Why do the LUN's show up in Device Manager/Disk drives but not in Disk management?
Thanks
Suresh
You'd think the LUNs are fine (and the fact they're actually just a file on the Netapp won't matter as it's a file system issue).
I assume something like fdisk /fixmbr or the recovery console were no use to you (disclaimer: work on a flexclone or at least make sure you have a snapshot before trying that!)?
There are commercial products (such as http://www.partition-recovery.com/) but I can't vouch for their effectiveness.
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Suresh Rajagopalan Sent: 23 December 2009 07:26 To: toasters@mathworks.com Subject: Fixing corrupted NTFS LUN's
Following up on my post, we had HBA and path issues causing LUN corruption on several NTFS LUN's on the original host. As a result, we cannot even see a partition table on the LUN's.
Are there any utilities to manipulate or repair NTFS LUN files (which are visible as flat files via the CIFS share to the volume)?
Thanks Suresh
From: Suresh Rajagopalan Sent: Tuesday, December 22, 2009 7:38 PM To: toasters@mathworks.com Subject: Cannot see LUNs after server move
We had a bunch of NTFS LUN's on a server that crashed (2003x64/Snapdrive 4.2.1). We are trying to move the LUNS to another server(Snapdrive 6/Win2k3x64). To do this we did the following:
1) Unmap old initiator from lun 2) Zone new server to the Netapp filer. 3) Try to use connect disk from new server to the lun 4) This gives a error saying drive notification timeout
To debug this more, I opened Disk Management. The disks do not show up there either. But they show up as LUNs under Device manager. Why do the LUN's show up in Device Manager/Disk drives but not in Disk management?
Thanks Suresh
To report this email as spam click here https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg== YULZDgGNd5P2IH7AuKzJjhTUVeUIU7ENJ4owyNC8RpgWkw== .
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
If the disks (read LUNs) do not appear to windows as a disk then a Windows based disk recover tool will also not see the drive to recover - e.g. for these to work it would need to see a disk drive and see no or corrupt file/partition system to fix it.
Suggest you look at an Linux boot CD/DVD that has iSCSI support to see if it can mount it as a NTFS volume. (follow Darren Sykes advise so as not to break it further)
A quick google for a tool to recover LUNs does not look very promising - good luck and please post back if you do find something.
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Darren Sykes Sent: Wednesday, 23 December 2009 8:51 PM To: Suresh Rajagopalan; toasters@mathworks.com Subject: RE: Fixing corrupted NTFS LUN's
You'd think the LUNs are fine (and the fact they're actually just a file on the Netapp won't matter as it's a file system issue).
I assume something like fdisk /fixmbr or the recovery console were no use to you (disclaimer: work on a flexclone or at least make sure you have a snapshot before trying that!)?
There are commercial products (such as http://www.partition-recovery.com/) but I can't vouch for their effectiveness.
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Suresh Rajagopalan Sent: 23 December 2009 07:26 To: toasters@mathworks.com Subject: Fixing corrupted NTFS LUN's
Following up on my post, we had HBA and path issues causing LUN corruption on several NTFS LUN's on the original host. As a result, we cannot even see a partition table on the LUN's.
Are there any utilities to manipulate or repair NTFS LUN files (which are visible as flat files via the CIFS share to the volume)?
Thanks Suresh
From: Suresh Rajagopalan Sent: Tuesday, December 22, 2009 7:38 PM To: toasters@mathworks.com Subject: Cannot see LUNs after server move
We had a bunch of NTFS LUN's on a server that crashed (2003x64/Snapdrive 4.2.1). We are trying to move the LUNS to another server(Snapdrive 6/Win2k3x64). To do this we did the following:
1) Unmap old initiator from lun 2) Zone new server to the Netapp filer. 3) Try to use connect disk from new server to the lun 4) This gives a error saying drive notification timeout
To debug this more, I opened Disk Management. The disks do not show up there either. But they show up as LUNs under Device manager. Why do the LUN's show up in Device Manager/Disk drives but not in Disk management?
Thanks Suresh
To report this email as spam click herehttps://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==.
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************
-
chaim rieger -
Darren Sykes -
Michael Schipp -
Milazzo Giacomo -
Page, Jeremy -
Romeo Theriault -
Suresh Rajagopalan