toasters April 1999

toasters@lists.teaparty.net

117 participants
153 discussions

RE: Swapping disks between shelves (F740 cluster upgrade)
by Dawn Hamel 13 Apr '99

13 Apr '99

When you place the drives from the "old" filer into the drive bays of the "new filer", I would suggest that you boot from floppy and make sure that the new filer can see all the drives. Since you are using a new "head" ... then you are also going to be using a new NVRAM card. The NVRAM actually puts an entry into the labels of the disks so that the disks know that this data belongs to this filer/NVRAM card. This is just in case there is any leftover data in the NVRAM card before shutdown ... When you boot, the filer will want to re-write the labels on the new drives placing the new NVRAM card signature onto the raid labels ... If you boot and all the drives are not seen, some of the labels will be re-written and some will not. You will then have mismatch raid labels and the machine will not boot (too many disks missing from the raid array) ... You will then need to go in and edit the raid labels (not fun) So ... the short of all this is to boot from floppy and make sure that the new filer sees ALL the disks -----Original Message----- From: Jay Soffian [mailto:jay@cimedia.com] Sent: Friday, April 09, 1999 8:33 PM To: toasters(a)mathworks.com Subject: Swapping disks between shelves (F740 cluster upgrade) We have an F740 with three FC-AL shelves and 15 9GB disks. The shelves only have a single LRC. We are getting a new F740 and everything we need in order to setup the two F740's to do CF. The new shelves will have two LRCs as required for CF. In order to minimize downtime while we are upgrading our current shelves with a second LRC, we'd like to setup the new filer next to the current filer, then swap all of the disks from our current filer into the new shelves. I am assuming that if we do this, when we power up the new filer, it will assume the identity of our current filer. Then we can upgrade our current shelves at our leisure. Does this sound like it will work? Are there any compatibility issues between drives and shelves? Any other words of advice about upgrading to CF? Thanks. j. -- Jay Soffian <jay(a)cimedia.com> UNIX Systems Administrator 404.572.1941 Cox Interactive Media

1 0

RE: Not a server
by Benn, Paul 12 Apr '99

12 Apr '99

This may sound too simple but it seems as if there is no physical connection between the filer and the NT box. It doesn't really sound like a filer specific issue. Is it safe to assume that you're using the NetWare Migration Tool that ships with NT server and that the NT server has TCP/IP installed and configured? Is the filer licensed for CIFS and does it have a machine account in the domain? Can you see the filer from the NT server when NOT outside of the NWM Tool? Sorry for the list of questions. Just checking the basics. Regards, Paul -----Original Message----- From: JD Ambagtsheer [mailto:J.D.Ambagtsheer@fel.tno.nl] Sent: Friday, April 09, 1999 7:05 AM To: toasters(a)mathworks.com Subject: Not a server I'm a Student and working on a migration project. Now I have the following question: I want to migrate from Novell Netware 3.x to my Netapp (F720). I want to realise this with a programm called "Netware Migration tool (Nwconv). If I want to choose a Windows NT server and I select the Netapp (he is in a domain called D00) the programm comes back with the following problem: "cannot connect to server: The Network name cannot be found". I don't know if this is a problem on the Netapp (perhaps a services or something) or that I have to look somewhere else Greetings, Jan-Dirk

2 1

Re: Upgrade F330 to Data ONTAP 5.2.1
by Daniel Quinlan 10 Apr '99

10 Apr '99

Ibrahima Bah <abe(a)netapp.com> writes: > I will just suggest you make sure that all clients mounting the filer > running 4.0.1c are unmounted before you proceed to upgrade. Otherwise > after the upgrade you will have stale NFS file errors on all your > clients and you will need to reboot all clients to fix it. The 4.0.1c > had NFS over TCP on by default. Stale NFS file errors are different from the NFS over TCP problem. I could be wrong, but I don't remember stale filehandles being an issue except for certain broken *down*grades. Check the upgrade notes. In addition to switching all clients to UDP, you can put this line into your rc file right before you reboot. options nfs.tcp.enable on You can still switch clients to UDP, but you won't have to wait until every last one has switched this way. - Dan

1 0

Swapping disks between shelves (F740 cluster upgrade)
by Jay Soffian 10 Apr '99

10 Apr '99

We have an F740 with three FC-AL shelves and 15 9GB disks. The shelves only have a single LRC. We are getting a new F740 and everything we need in order to setup the two F740's to do CF. The new shelves will have two LRCs as required for CF. In order to minimize downtime while we are upgrading our current shelves with a second LRC, we'd like to setup the new filer next to the current filer, then swap all of the disks from our current filer into the new shelves. I am assuming that if we do this, when we power up the new filer, it will assume the identity of our current filer. Then we can upgrade our current shelves at our leisure. Does this sound like it will work? Are there any compatibility issues between drives and shelves? Any other words of advice about upgrading to CF? Thanks. j. -- Jay Soffian <jay(a)cimedia.com> UNIX Systems Administrator 404.572.1941 Cox Interactive Media

1 0

Need help regarding quotas
by Patrick.Day.B＠bayer.com 09 Apr '99

09 Apr '99

We are currently migrating the home directories of 1200 users to our 740 (dot 5.2.1) All of our clients are either NT 4.0 (85%) or Win 95 (15%) and the filesystem on the netfiler is NT only. The quota file is configured as such: * user@/vol/uservol/users 100M #default Users Which should give everyone a 100Mb limit by default. Immediately after moving a user (with BackupExec-thus preserving the acl's) i run a program from TrustedSystems called reacle.exe that will allow me to force ownership of the files to the proper owner. All this said and done, the quotas are working correctly (no error messages) and are showing the users and thier limits. However, the actual file space accredited to the users is incorrect. It seems that only the files that they, themselves touch are assigned to them. I have users who i know are owners of more than 100Mb of files who, when the quota report is running, only appear to have 40K credited to them. Here is an example report for users who have more than 80Mb in their home directories. Type ID Volume Tree Used Limit Used Limit Quota Specifier ----- -------- -------- -------- ------- ------- -------- -------- ----------------- user * uservol users 0 102400 0 * user exral uservol users 2260 102400 29 user exjjr uservol users 90876 102400 188 user extyd uservol users 20 102400 3 user exjaw uservol users 1212 102400 4 user exaau uservol users 1692 102400 36 user exusl uservol users 960 102400 10 user extxf uservol users 168 102400 8 user exjec uservol users 4332 102400 15 user mitji uservol users 1336 102400 2 Is there anything i need to do that doesn't require user interaction? Any input would be appreciated. --Patrick Day System Admin. Bayer Corporation.

5 8

Anybody using an ADIC VLS DLT changer with their filer?
by Jaye Mathisen 09 Apr '99

09 Apr '99

I'm not having much luck with it unloading and sequencing the next tape...

1 0

Microsoft Appliances?
by Paul English 09 Apr '99

09 Apr '99

Oh boy, I can't wait, hold me back. http://www.news.com/News/Item/0,4,34836,00.html I think I'll stick with a toaster... -- Paul English (Tallpaul) (508) 647-7715 tallpaul(a)mathworks.com (508) 647-7015 FAX Walkie Channel 2

3 2

RE: Ridiculously easy question...
by Will Harper 09 Apr '99

09 Apr '99

This really isn't a simple question. First, is the app running as a service, or is the machine left with a "user" logged on? I presume you are talking about the app running on an NT server... If the app is running as a user, the problem is trivial, put a net use command in that user's logon script. If the app is running as a service, (and nobody is logged on when it is running), the plot thickens. There is NO CLEAN answer that I know of. There are some NT registry hacks to run an application at startup. This app can be a script. Alternately, you can run a script from the windows AT command (or the easier WINAT, inf the resource kit). The main issue will be making sure the same "username" is running all of the processes, because of possible conflicts in permissions. Attached are a couple of clippings from TechNet, which MAY work. I haven't tried them. Good luck Will Harper, MCSE -----Original Message----- From: Jaye Mathisen [SMTP:mrcpu@internetcds.com] Sent: Thursday, April 08, 1999 3:53 PM To: toasters(a)mathworks.com Subject: Ridiculously easy question... I'm just starting to use CIFS, and everything works fine, except one minor problem... I would like NT (4.0SP4, if it matters), to attach a drive on system startup, rather than having to be logged in... For various reasons, I cannot use UNC paths in my application, so I need to map the drive when the system boots, with a username and password... Is this possible? My filer is running 4.3.4, but I think I'm going to upgrade tonight to 5.2.1...

1 0

Not a server
by JD Ambagtsheer 09 Apr '99

09 Apr '99

I'm a Student and working on a migration project. Now I have the following question: I want to migrate from Novell Netware 3.x to my Netapp (F720). I want to realise this with a programm called "Netware Migration tool (Nwconv). If I want to choose a Windows NT server and I select the Netapp (he is in a domain called D00) the programm comes back with the following problem: "cannot connect to server: The Network name cannot be found". I don't know if this is a problem on the Netapp (perhaps a services or something) or that I have to look somewhere else Greetings, Jan-Dirk

1 0

Re: Need help regarding quotas
by sirbruce＠ix.netcom.com 09 Apr '99

09 Apr '99

On 04/09/99 00:05:17 you wrote: >Our problem is that it displays too much. We automount each user's home >directory. Since we want to permit them to write into each others >directory we have quotas on the qtree housing users' directories. >Unfortunately that file system is mounted once for every user :(((((((((. >Running quota -v displays data related to every home directory mounted on >the box. Unfortunately, it appears that Sun does not support the >automounter ":" path option in Solaris 2.6 which would fix the problem. How about just mounting the filesystems noquota? The filer won't care. >We automount each users home directory because we want to have a >data location independent pathing, i.e. /home/tkaczma instead of >/home/filer2/tkaczma. This prevents a lot of headaches when users' >directories are moved for some reason, like due to disaster recovery or >some migration. You might consider using symlinks instead. Bruce

2 1

← Newer
1
...
8
9
10
11
12
13
14
15
16
Older →

Jump to page:

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 April 1999