toasters June 2008

toasters@lists.teaparty.net

58 participants
52 discussions

Netapp and VMware... It's all so confusing!
by Timothy Hollingworth 01 Apr '10

01 Apr '10

So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3. The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the … [View More]

11 15

how to "move" an existing snapmirror to new network interfaces?
by Todd C. Merrill 18 Aug '08

18 Aug '08

I have lots of existing q-tree snapmirrrors of the form: srcfiler:/vol/volM/qtreeX destfiler:/vol/volN/qtreeY "srcfiler" (DNS name) is the e11 interface on srcfiler "destfiler" (DNS name) is the e9a interface on destfiler We just built a "dedicated snapmirror/backup" network and added the following: "srcfiler-backup" (DNS name) is the e0 inteface on srcfiler "destfiler-backup" (DNS name) is the e11a interface on destfiler Subsequent 'snapmirror update -S ...' commands (we don't use … [View More]

5 7

RE: filer to vfiler conversions
by Villabroza, Gerald 01 Jul '08

01 Jul '08

Because each vfiler needs its own ip address there may not be a way to unassign the ip from the root vfiler (vfiler0) and assign it to a vfiler (vfiler1) with zero downtime. You can certainly use a new ip for vfiler1 and make DNS changes so the old name points to the new ip. This isn't zero downtime, but depending on your DNS mechanics it can be very low. If you're running cifs on vfiler0 and want to move those resources to vfiler1 you have no choice but to take a short outage since cifs is … [View More]

2 1

Replacing Disk Shelves
by ifstat 30 Jun '08

30 Jun '08

Hi Toasters, A customer of mine has reached the limit on the FAS3050C, in terms of shelves and disks. So inorder to allocate additional storage space, we are replacing the 36gb disk with 300gb. However, we also need to replace the DS14, with DS14MK4 shelves becuase of better throughput between DS14 & DS14MK4. Can someone please confirm the proceedure of doing this without interuption. Logic says that: 1) Destroy any aggregates on the 36Gb disks. 2) Zero all spares 3) Remove ownership … [View More]

2 1

Re: R: Deleting files from snapshots
by Francois Joubert 27 Jun '08

27 Jun '08

Yes, but we have no tapes :) Francois Page, Jeremy wrote: > Would the software vendor require you to delete that file off your tapes > too? I think that's what James was asking. > > > -----Original Message----- > From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] > On Behalf Of Francois Joubert > Sent: Friday, June 27, 2008 5:12 AM > To: James Beal > Cc: NetApp Toasters List > Subject: Re: R: Deleting files from snapshots > > We … [View More]

3 2

SnapManager SQL Errors
by Raj Patel 27 Jun '08

27 Jun '08

Hi, We're just setting up a new SQL server with a SMSQL backup job and we're seeing the following DBCC errors. The SM SQL job has been re-installed and the job setup again as per other servers (ie its the first time we've seen the error). There is also an initiator error but we're not sure why thats listed as an issue - it through the initiator and that IP that the SAN lun's are connected in the first place - [09:22:04.916] *** VERIFY DATABASE AFTER BACKUP 09:22:04.916] Collecting … [View More]

5 6

Re: R: Deleting files from snapshots
by Francois Joubert 27 Jun '08

27 Jun '08

We have no tapes; historical backup is in many online snapvault copies. Francois James Beal wrote: > Are you going to destroy all the backup tapes ?

1 0

Re: SnapManager SQL Errors
by Raj Patel 27 Jun '08

27 Jun '08

Oliver pointed me in the right direction - After the email to check the preferred SAN address I noticed the SAN was connected via the Data VLAN and not the iSCSI VLAN. The DBA's had also renamed the server which meant the initiator was keeping the drive mapped but it was possibly affecting mounting the snaps – I disconnected and reconnected with an updated initiator name to match the new server name & reconnected on the correct VLAN and it sorted things out. Cheers, Raj. On Fri, Jun 27, … [View More]2008 at 11:52 AM, Uddhav Regmi <uddhav.regmi(a)worldnet.att.net> wrote: > Raj, > SWs looks OK and OS too. > > [09:22:05.681] [SnapDrive Error]: There are no initiators >> connected to the filer "10.1.46.1". >> >> (SnapDrive Error Code: 0xc00402e6) >> >> [09:22:05.697] Error Code: 0xc00408f0 > > > what does this show > > filer> iscsi initiator show > No initiators connected === something like this ? > > is this turn on ? > > > > > > Its little tricky to make it work inside the ESX.... > > We use the tool esxcfg-swiscsi to configure it. The software iSCSI initiator > in the VMkernel has a dependency upon the service console, therefore both > the service console and VMkernel must have an IP route to the iSCSI target. > 1. Add a VMkernel port to a vSwitch that has an uplink and route to iSCSI > target > 2. Ensure service console IP interface has a route to the same iSCSI target > 3. Using either the VI Client security profile or the esxcfg-firewall, open > a port in the service console firewall for iSCSI (TCP:3260) > 4. In the command line, enable iSCSI with esxcfg-swiscsi -e command > 5. In the command line, run > 6. At the service console command line, run esxcfg-swiscsi -s > 7. In the VI Client your iSCSI target should become visible. > Open the iSCSI tab in your ESX Server configuration and add the dynamic > address of you filer, probably the same IP as your gateway. > > are these all done > > Can you access the resources from ESX box ( SQL ) to filer ? Even before > heading for backup > > this is interesting, let me know. Please put me in loop > > -----Original Message----- > From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On > Behalf Of Raj Patel > Sent: Thursday, June 26, 2008 4:28 PM > To: Uddhav Regmi > Cc: NetApp Toasters List > Subject: Re: SnapManager SQL Errors > > Hi, > > Its a Windows 2003 sp 2 VM server (running on ESX 3.5) using SnapDrive > 4.2.1 and SMSQL 2.1.1 and SQL 2005 > > Three luns f:/g:/h: for database, logs & tmpdb > > Verification server is the same as the SQL server (ie it does its own > dbcc check) > > The SAN connection is via IP address - what needs to be able to > resolve to what ? The SQL server can resolve the SAN and vice versa. > > Cheers, > Raj. > > > > On Thu, Jun 26, 2008 at 10:44 PM, Uddhav Regmi > <uddhav.regmi(a)worldnet.att.net> wrote: >> Raj, >> Can you elaborate more here..... >> >> a) platform infrastructure >> b) SME, Snapdrie, SQL versions >> c) is verification Server and SQL server where you installed SME are same >> server or different server >> d) does the nslookup resolve all the names correctly from all three >> locations >> e) any Dual/multi path involved here.... >> this is interesting error >> >> ~uddhav >> >> -----Original Message----- >> From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] > On >> Behalf Of Raj Patel >> Sent: Wednesday, June 25, 2008 6:49 PM >> To: NetApp Toasters List >> Subject: SnapManager SQL Errors >> >> Hi, >> >> We're just setting up a new SQL server with a SMSQL backup job and >> we're seeing the following DBCC errors. The SM SQL job has been >> re-installed and the job setup again as per other servers (ie its the >> first time we've seen the error). There is also an initiator error but >> we're not sure why thats listed as an issue - it through the initiator >> and that IP that the SAN lun's are connected in the first place - >> >> [09:22:04.916] *** VERIFY DATABASE AFTER BACKUP >> >> >> 09:22:04.916] Collecting verification information... >> [09:22:04.916] Getting database backup information from SnapInfo > file... >> [09:22:04.916] Running verification from local server.... >> [09:22:04.931] Mounting Snapshot [sqlsnap__server-sql1__recent] >> for Virtual Disk F of Computer server-sql1 >> [09:22:05.322] WARNING: Unable to get default mount point directory >> [09:22:05.322] Snapshot will be mounted on subdirectory [MPDisk001] >> [09:22:05.681] [SnapDrive Error]: There are no initiators >> connected to the filer "10.1.46.1". >> >> (SnapDrive Error Code: 0xc00402e6) >> >> [09:22:05.697] Error Code: 0xc00408f0 >> There are no initiators connected to the filer from verification >> server. Please check SnapManager report and Event logs for details. >> >> Any ideas ? >> >> Thanks in advance, >> Raj. >> >> > [View Less]

1 0

Re: SnapManager SQL Errors
by Raj Patel 26 Jun '08

26 Jun '08

Hi, Its a Windows 2003 sp 2 VM server (running on ESX 3.5) using SnapDrive 4.2.1 and SMSQL 2.1.1 and SQL 2005 Three luns f:/g:/h: for database, logs & tmpdb Verification server is the same as the SQL server (ie it does its own dbcc check) The SAN connection is via IP address - what needs to be able to resolve to what ? The SQL server can resolve the SAN and vice versa. Cheers, Raj. On Thu, Jun 26, 2008 at 10:44 PM, Uddhav Regmi <uddhav.regmi(a)worldnet.att.net> wrote: > Raj,… [View More]

2 1

Re: Deleting files from snapshots
by Fox, Adam 26 Jun '08

26 Jun '08

There is no approved or unapproved way to do this. It's not possible. The closest thing you can do is to put a Datafort in front of the controller and encrypt everything. Then you can shred the keys that encrypted the files in question. It doesn't delete them per se but it makes them unreadable. -- Adam Fox ------------------------ Typed with my thumbs on a very small keyboard. ----- Original Message ----- From: Francois Joubert <francois.joubert(a)imagination.com> To: NetApp … [View More]

1 0

2025

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 June 2008