toasters January 2010

toasters@lists.teaparty.net

23 participants
14 discussions

Re: Question about moving a shelf that is used for vmware iscsi datastores between filers
by Romeo Theriault 07 Jan '10

07 Jan '10

For future reference for others on the mailing list who might try a similar procedure in the future I also received a useful response from Matt Hallmark which points out that you also need to keep the target portal group tags the same for *nix/esx hosts. On Thu, Jan 7, 2010 at 8:39 AM, Matt Hallmark <matt(a)cosmictoaster.com>wrote: > You will run into trouble, with all *nix/esx hosts if the iSCSI Target > Portal Group tag(s) change. > > goliath> iscsi tpgroup show > TPGTag Name Member Interfaces > 1 e0a_old (none) > 1004 e3a_default e3a > 1005 e3b_default e3b > 2000 VIF_e0_AC_default VIF_e0_AC > 2001 VIF_e0_BD_default VIF_e0_BD > > Those are changable, but would require an iSCSI maintenance window to > complete. > > Matt Romeo

1 0

Re: Question about moving a shelf that is used for vmware iscsi datastores between filers
by Romeo Theriault 07 Jan '10

07 Jan '10

> According to this you should be fine: > > http://www.vmware.com/files/pdf/vmfs_resig.pdf > Great, this is exactly what I was looking for. This clearly explains how vmware determines which datastore is which: When you define a new VMFS volume on a block device, VMFS calculates a > volume signature and writes it in the header of the VMFS volume. This volume > signature is a combination of the LUN number, as seen by that ESX host, and > the disk serial number as the storage array reports it to the ESX host. > VMFS volume signature = LUN number + disk serial number > So it seems that if I keep the lun serial numbers the same across the move, and remap the luns to the same lun id's vmware will recognize the datastores as the original datastores. Thanks for the help everyone, -- Romeo Theriault System Administrator Information Technology Services

1 0

Issues mounting snapshot
by Raj Patel 07 Jan '10

07 Jan '10

Hi, Simple problem - I have a SQL server (Windows 2008, 64 bit, SQL 2008, Snapdrive 6.1 & snapmanager sql 5.0.0.38 (both 64bit) Snapshots work fine - however the dbcc check fails when it attempts to mount the snapshot for a verification. Now - I am able to mount the snapshot on a Windows 2003, 32 bit box running Snapdrive 6.1 so I'm fairly certain its not a volume space issue. The actual error I get is 'A timeout of 120 secs elapsed while waiting for volume arrival notification from the operating system' - this happens when I use the SD GUI to manually mount the snapshot. The console shows pretty much the same sort of error if I watch it while running the GUI mount. We have this working fine on other SQL servers and its just started happening on this box. Any ideas ? Our DBA's are starting to wonder if the aggravation of troubleshooting SM SQL / SD issues is worth the convenience of instant snapshots. At least with traditional backups they know where they stand. Thanks in advance, Raj.

3 4

Question about moving a shelf that is used for vmware iscsi datastores between filers
by Romeo Theriault 07 Jan '10

07 Jan '10

Sorry if this post is a bit off-topic as it may relate more to vmware than netapp but I'm hoping it relates enough to netapp that it's ok. Scenario is: I have two netapp filers and both are being used solely for a single vmware cluster which has access to both filers for use as iscsi (and only iscsi) datastores. I need to move one shelf (aggregate) on one of the filers to the other filer. I'm comfortable with the netapp side of things but am unsure if anything special needs to happen on the vmware side for it to recognize the datastores now that they are on the other head. I've simulated a test by snapmirroring a test datastore to the other head, unmapping the old lun, changing the lun serial of the new lun to the old luns, mapping the new lun back to the same lun id that the old lun was using and vmware was content with this (i.e. it saw the datastore as the original with all it's content). Will moving a shelf with several datastores to the other head work as well? Thanks for any help. -- Romeo Theriault System Administrator Information Technology Services

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters January 2010