toasters

toasters@lists.teaparty.net

13515 discussions

RE: Why is root not root?
by Mike Sphar 25 May '01

25 May '01

Speaking of that, I ran into some interesting behavior the other day. I'd had a recurrent problem where our build scripts couldn't delete a directory from the previous build because some windows user somewhere had left a window open on that share. Well, I eventually discovered that by making the share read-only at the share level for everyone but our build engineers, that if I opened a window in that share, and then deleted it from UNIX, the delete would work and in fact my open window would automatically close. However, we later found that the behavior was slightly different if the windows client was viewing the share through an Explorer window (i.e. using the double-paned File Explorer interface rather than just an open window. Anyway, we found that when the share was accessed via Explorer, then when the rm command was executed from UNIX, the command would return successfully with no error, but the directory still remained. If I then closed the Explorer window, the directory would disappear. This was actually worse behavior from the build engineers perspective because at least before their scripts would get a permission denied error and exit, rather than continuing on assuming their work area was empty. I suspect this is for the most part standard CIFS behavior, but it's still a little bizarre to see the rules applied differently depending on which tool was being used on the client. Having said all that, yes I too would like an option whereby files or directories could be deleted no matter what their locking state was. This problem has been an unending source of complaints from our build engineers who ask questions like "Can we go back to the server where this wasn't a problem?" That server being an old Sparc running NFS and Samba. Obviously I don't want to go back to that old beast. -----Original Message---- From: Bruce Sterling Woodcock [mailto:sirbruce@ix.netcom.com] Sent: Friday, May 25, 2001 4:25 AM To: Muhlestein, Mark; White, Lance; 'Chuck Ross'; Net App List (E-mail) Subject: Re: Why is root not root? How about letting root delete files that are currently locked open on the NT-side like they can with NFS-locked files? Bruce

1 0

RE: Locking of Files and server clusters
by White, Lance 25 May '01

25 May '01

Come to think of it, so long as you exit with a value of 0, you shouldn't need the if...then statements. Just fire off an rsh for both nodes to terminate the sessions from the host. One will work, the other won't, but it shouldn't matter. i.e. rsh Filer -l ClusterAdmin cifs terminate -t 0 node1; rsh Filer -l ClusterAdmin cifs terminate -t 0 node2; exit 0; Again, you MIGHT want to wrap some error checking logic around this to feedback results, etc. Lance -----Original Message----- From: White, Lance [mailto:Lance.White@netapp.com] Sent: Friday, May 25, 2001 8:16 AM To: 'Morgan, Joshua'; 'toasters(a)mathworks.com' Subject: RE: Locking of Files and server clusters One of the steps required to ensure proper failover of SQL Server via Legato Cluster is the creation of a Resource Group (RG)connecting the application to the two nodes. The RG must include a script that gets executed as one of the first steps in bringing up the RG. The script was designed to be a workaround for the filer's normally necessary CIFS file-locking behavior. When an Legato Cluster node first fails, as far as the filer is concerned, the session between the filer and that node is still alive (the disconnect could be temporary). Because of this, it initially maintains the file locks originally established for that session. Without our script, these locks would prevent the other "takeover" node from accessing the required files during takeover. However, when our script is implemented, the file locks are terminated and the "takeover" node can access the files as necessary. In our case, the files the "takeover" node needs access to are the SQL Server database data and! log files. If the "takeover" node does not have access to these files, once the takeover is completed and the SQL Server is done recovering, the databases on the filer are declared "suspect". Following is the generic syntax for the script that must reside on each node: rsh filer_name -l cluster_admin_name cifs terminate -t 0 failed_node_name You can pass the name of the failed node via a &ft' environment variable (refer to the LCE docs for details), or you can create a nested if...then...else loop to determine which node you are starting up on, and how to terminate the CIFS session on the Filer. An example would be: if &ft'currentnode == 'failednode' then rsh Filer -l ClusterAdmin cifs terminate -t 0 failednode else rsh Filer -l ClusterAdmin cifs terminate -t 0 othernode end; Likely will be a little more coding than this, but you get the drift. Lance White Systems Engineer Network Appliance -----Original Message----- From: Morgan, Joshua [mailto:JMorgan@Trivergent.com] Sent: Friday, May 25, 2001 7:29 AM To: 'toasters(a)mathworks.com' Subject: Locking of Files and server clusters Here is the Scenario: We have SQL7 Server running with its Databases on an F760 We are using Legato Clustering Software If the main SQL Server dies and the cluster software tries to bring up the backup server, we get a message saying that the Database files are still locked by the downed server. Does anyone know of a way to script unlocking the files? We can manually do it through server manager but that is no good for Disater Recovery. Joshua Morgan PH: (864) 331-7939 jmorgan(a)trivergent.com

1 0

RE: Locking of Files and server clusters
by White, Lance 25 May '01

25 May '01

One of the steps required to ensure proper failover of SQL Server via Legato Cluster is the creation of a Resource Group (RG)connecting the application to the two nodes. The RG must include a script that gets executed as one of the first steps in bringing up the RG. The script was designed to be a workaround for the filer's normally necessary CIFS file-locking behavior. When an Legato Cluster node first fails, as far as the filer is concerned, the session between the filer and that node is still alive (the disconnect could be temporary). Because of this, it initially maintains the file locks originally established for that session. Without our script, these locks would prevent the other "takeover" node from accessing the required files during takeover. However, when our script is implemented, the file locks are terminated and the "takeover" node can access the files as necessary. In our case, the files the "takeover" node needs access to are the SQL Server database data and! log files. If the "takeover" node does not have access to these files, once the takeover is completed and the SQL Server is done recovering, the databases on the filer are declared "suspect". Following is the generic syntax for the script that must reside on each node: rsh filer_name -l cluster_admin_name cifs terminate -t 0 failed_node_name You can pass the name of the failed node via a &ft' environment variable (refer to the LCE docs for details), or you can create a nested if...then...else loop to determine which node you are starting up on, and how to terminate the CIFS session on the Filer. An example would be: if &ft'currentnode == 'failednode' then rsh Filer -l ClusterAdmin cifs terminate -t 0 failednode else rsh Filer -l ClusterAdmin cifs terminate -t 0 othernode end; Likely will be a little more coding than this, but you get the drift. Lance White Systems Engineer Network Appliance -----Original Message----- From: Morgan, Joshua [mailto:JMorgan@Trivergent.com] Sent: Friday, May 25, 2001 7:29 AM To: 'toasters(a)mathworks.com' Subject: Locking of Files and server clusters Here is the Scenario: We have SQL7 Server running with its Databases on an F760 We are using Legato Clustering Software If the main SQL Server dies and the cluster software tries to bring up the backup server, we get a message saying that the Database files are still locked by the downed server. Does anyone know of a way to script unlocking the files? We can manually do it through server manager but that is no good for Disater Recovery. Joshua Morgan PH: (864) 331-7939 jmorgan(a)trivergent.com

1 0

How to configure?
by Jordan Share 25 May '01

25 May '01

So, we are looking at getting a 720 (possibly a used 740) in the near future. How should I configure it wrt number of volumes and so forth? Is there a FAQ somewhere where I can read about the theory behind volume configuration? Basically, I've seen posts that make me think it might be nice to have one volume just for the root filesystem, and another for the actual data we'll be using. What are the restrictions on volumes and so forth? Can I have a 2 volumes in a RAID set, or no? I'd just like a pointer towards a FAQ, when you come down to it, I realize these questions are quite vague. :) Thanks, Jordan

2 1

Locking of Files and server clusters
by Morgan, Joshua 25 May '01

25 May '01

Here is the Scenario: We have SQL7 Server running with its Databases on an F760 We are using Legato Clustering Software If the main SQL Server dies and the cluster software tries to bring up the backup server, we get a message saying that the Database files are still locked by the downed server. Does anyone know of a way to script unlocking the files? We can manually do it through server manager but that is no good for Disater Recovery. Joshua Morgan PH: (864) 331-7939 jmorgan(a)trivergent.com

1 0

RE: Why is root not root?
by Chuck Ross 25 May '01

25 May '01

Yep, set the ignore_acl option and it works great! Thanks guys. Chuck Ross > -----Original Message----- > From: White, Lance [mailto:Lance.White@netapp.com] > Sent: Thursday, May 24, 2001 5:59 PM > To: Knight, Graham; Chuck Ross; Net App List (E-mail) > Subject: RE: Why is root not root? > > > Ah yes, I remember using this one. Nice memory, Graham! > Hopefully that's the right answer for you, Chuck. Let us know! > > LW > > -----Original Message----- > From: Knight, Graham [mailto:Graham.Knight@netapp.com] > Sent: Thursday, May 24, 2001 2:49 PM > To: 'Chuck Ross'; Net App List (E-mail) > Subject: RE: Why is root not root? > > > > Probably because the file has an NT ACL that has been set so > tightly that > the root user cannot access it without taking ownership > first, which cannot > be done very easily from the command line. > > Setting this (hidden) option will make this type of problem a > thing of the past: > > options cifs.nfs_root_ignore_acl on > > I used this extensively at my last position with very good results. > > Graham > > > -----Original Message----- > From: Chuck Ross [mailto:chuck.ross@signiant.com] > Sent: Thursday, May 24, 2001 3:06 PM > To: Net App List (E-mail) > Subject: Why is root not root? > > > Hi all, > > Why is root on a Unix admin host for a filer in a mixed env not really > root? By that I mean why is it possible to create directories on the > NetApp via a Cifs share that root has no access to? > > Chuck Ross > > SIGNIANT - A Nortel Networks Venture > 1550 Carling Avenue, Suite 101 > Ottawa, ON > K1Z 8S8 > > email: Chuck.Ross(a)signiant.com > tel: (613) 761-3605 > fax: (613) 761-3629 >

1 0

RE: Why is root not root?
by Muhlestein, Mark 25 May '01

25 May '01

This is explained in the security troubleshooter. "I'm root but I can't do everything I want to on the filer" http://now.netapp.com/NOW/knowledge/docs/olio/guides/53_troubleshooting/faq… By default, NT security does not allow administrators to access data unless it is granted in the ACL. However, NT administrators can take ownership and grant themselves access. Not all shops want this behavior. In particular, if you have a Unix-centric administration model you can have "root" override NT-style security by turning on the "cifs.nfs_root_ignore_acl" option. That option is available in 5.3.7 and later versions of ONTAP. Mark -----Original Message----- From: White, Lance [mailto:Lance.White@netapp.com] Sent: Thursday, May 24, 2001 2:16 PM To: 'Chuck Ross'; Net App List (E-mail) Subject: RE: Why is root not root? Because Data OnTap is NOT Unix. 'root' is a privileged account, 'Administrator' is a privileged account, some people map root == Administrator if they're really concerned. I would believe that allowing this degree of flexibility is a "feature". -----Original Message----- From: Chuck Ross [mailto:chuck.ross@signiant.com] Sent: Thursday, May 24, 2001 2:06 PM To: Net App List (E-mail) Subject: Why is root not root? Hi all, Why is root on a Unix admin host for a filer in a mixed env not really root? By that I mean why is it possible to create directories on the NetApp via a Cifs share that root has no access to? Chuck Ross SIGNIANT - A Nortel Networks Venture 1550 Carling Avenue, Suite 101 Ottawa, ON K1Z 8S8 email: Chuck.Ross(a)signiant.com tel: (613) 761-3605 fax: (613) 761-3629

2 1

�h�h�h�hBICYCLE !! & FLASH SHOES!!�h�h�h�hBICYCLE !! & FLASH SHOES!!�h�h
by t141525504＠hotmail.com 25 May '01

25 May '01

1 0

DS14 experiences?
by Moshe Linzer 25 May '01

25 May '01

Is anybody using the new DS14 disk shelves? Are the shelves and drives reliable? My FC9's and 36GB drives have been rock solid for the past year or more, and I am leery of jumping into new technology. But getting twice the capacity in the same footprint is just too enticing! Moshe

2 1

RE: recovering data from user's snapshot directory?
by Muhlestein, Mark 24 May '01

24 May '01

You can use "scopy.exe" from the NT resource kit to get this data, since it uses backup-mode access which bypasses the security on the files. Mark -----Original Message----- From: brad(a)ThoughtWorks.com [mailto:brad@ThoughtWorks.com] Sent: Tuesday, May 22, 2001 2:23 PM To: toasters(a)mathworks.com Subject: recovering data from user's snapshot directory? We have a few employees that have left the company and I need to get their data back from their snapshot directories (the original files and folders were deleted as well as the usernames). The volume is a CIFS homedrive setup and if I try to take ownership of the folders under the snapshot directory, I cannot. I also cannot give myself read access to the folder. Has anyone else has this problem? I'm logging in via the administrator account and it still does not work. Thanks in advance for your help.

1 0

RE: Why is root not root?
by White, Lance 24 May '01

24 May '01

Ah yes, I remember using this one. Nice memory, Graham! Hopefully that's the right answer for you, Chuck. Let us know! LW -----Original Message----- From: Knight, Graham [mailto:Graham.Knight@netapp.com] Sent: Thursday, May 24, 2001 2:49 PM To: 'Chuck Ross'; Net App List (E-mail) Subject: RE: Why is root not root? Probably because the file has an NT ACL that has been set so tightly that the root user cannot access it without taking ownership first, which cannot be done very easily from the command line. Setting this (hidden) option will make this type of problem a thing of the past: options cifs.nfs_root_ignore_acl on I used this extensively at my last position with very good results. Graham -----Original Message----- From: Chuck Ross [mailto:chuck.ross@signiant.com] Sent: Thursday, May 24, 2001 3:06 PM To: Net App List (E-mail) Subject: Why is root not root? Hi all, Why is root on a Unix admin host for a filer in a mixed env not really root? By that I mean why is it possible to create directories on the NetApp via a Cifs share that root has no access to? Chuck Ross SIGNIANT - A Nortel Networks Venture 1550 Carling Avenue, Suite 101 Ottawa, ON K1Z 8S8 email: Chuck.Ross(a)signiant.com tel: (613) 761-3605 fax: (613) 761-3629

1 0

RE: Why is root not root?
by Chuck Ross 24 May '01

24 May '01

That's the problem, even with root == Administrator I still run into directories(folders) that I cannot access (as root). I don't have a problem with the flexibility, I just want to be able to manage my data from one machine, my admin host. Chuck > -----Original Message----- > From: White, Lance [mailto:Lance.White@netapp.com] > Sent: Thursday, May 24, 2001 5:16 PM > To: Chuck Ross; Net App List (E-mail) > Subject: RE: Why is root not root? > > > Because Data OnTap is NOT Unix. 'root' is a privileged > account, 'Administrator' is a privileged account, some people > map root == Administrator if they're really concerned. I > would believe that allowing this degree of flexibility is a "feature". > > -----Original Message----- > From: Chuck Ross [mailto:chuck.ross@signiant.com] > Sent: Thursday, May 24, 2001 2:06 PM > To: Net App List (E-mail) > Subject: Why is root not root? > > > Hi all, > > Why is root on a Unix admin host for a filer in a mixed env not really > root? By that I mean why is it possible to create directories on the > NetApp via a Cifs share that root has no access to? > > Chuck Ross >

1 0

RE: Why is root not root?
by White, Lance 24 May '01

24 May '01

Because Data OnTap is NOT Unix. 'root' is a privileged account, 'Administrator' is a privileged account, some people map root == Administrator if they're really concerned. I would believe that allowing this degree of flexibility is a "feature". -----Original Message----- From: Chuck Ross [mailto:chuck.ross@signiant.com] Sent: Thursday, May 24, 2001 2:06 PM To: Net App List (E-mail) Subject: Why is root not root? Hi all, Why is root on a Unix admin host for a filer in a mixed env not really root? By that I mean why is it possible to create directories on the NetApp via a Cifs share that root has no access to? Chuck Ross SIGNIANT - A Nortel Networks Venture 1550 Carling Avenue, Suite 101 Ottawa, ON K1Z 8S8 email: Chuck.Ross(a)signiant.com tel: (613) 761-3605 fax: (613) 761-3629

1 0

Why is root not root?
by Chuck Ross 24 May '01

24 May '01

Hi all, Why is root on a Unix admin host for a filer in a mixed env not really root? By that I mean why is it possible to create directories on the NetApp via a Cifs share that root has no access to? Chuck Ross SIGNIANT - A Nortel Networks Venture 1550 Carling Avenue, Suite 101 Ottawa, ON K1Z 8S8 email: Chuck.Ross(a)signiant.com tel: (613) 761-3605 fax: (613) 761-3629

1 0

RE: Question on "vol copy"
by Smith, Gil 24 May '01

24 May '01

> Do any of you know if the "vol copy" command can be used in > this case. Can I specify that the destination is actually a qtree? I would recommend you use ndmpcopy for this. Here is some info and an example: Here is the "ndmpcopy" info for migrating data between filers. It uses dump/restore and can be used for smaller paths (not entire volumes). You have to make sure that each filer trusts each other by making etc/hosts.equiv entries. There is also an actual test level 0 and level 9 below. It is a good tool to know how to use/get working. You can get a binary for ndmpcopy via anonymous ftp from our ftp.netapp.com as below or www.ndmp.org and compile it. ftp> cd ndmpcopy 250 "/pub/netapp/upload/ndmpcopy" is new cwd. ftp> dir 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. drwxrwxr-x 2 ftpuser ftpusers 4096 Apr 17 2000 aix drwxrwxr-x 2 ftpuser ftpusers 4096 Mar 29 2000 linux drwxrwxr-x 2 ftpuser ftpusers 4096 Oct 5 08:54 solaris drwxrwxr-x 2 ftpuser ftpusers 4096 Oct 5 06:52 solaris2.7 Using ndmpcopy for data migration Use the latest version of ndmpcopy. Version 1.2 and later has incremental support that works, and you no longer need to specify a password on the command line, it is promptable now. Refer to ndmpcopy documentation for client installation and command usage. Example using ndmpcopy Version 1.2: Set up the destination volume where the date will be copied to. Use ndmpcopy to do a level 0 dump: Example: ndmpcopy source:path_to_volume destination:path_to_volume -level 0 -dpass After the level 0 is done, a level 1 ndmpcopy may done. This will copy only the data that changed since the level 0: ndmpcopy source:path_to_volume destination:path_to_volume -level 1 -dpass When ready to use the new volume: Turn off NFS & CIFS on the source by executing nfs off and cifs terminate. Do a final incremental to copy changes since the last ndmpcopy: ndmpcopy source:path_to_volume destination:path_to_volume -level 9 -dpass Configure the volume for production use. This process maintains performance by keeping the data striped across all disks in the volume, and you would probably rather wait the extra few minutes of downtime for the ndmpcopy to complete and maintain performance, than lose a lot of performance to get it done quickly. Be sure to use the latest recommended Data ONTAP OS. [example from lab below] unix# ndmpcopy f760cl1-rtp:/vol/vol0/home f820-rtp:/vol/vol0/home -level 0 -dpass Source password: Destination password: Connecting to f760cl1-rtp. Connecting to f820-rtp. f760cl1-rtp: CONNECT: Connection established. f820-rtp: CONNECT: Connection established. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: creating "/vol/vol0/../snapshot_for_ba ckup.1" snapshot. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Using subtree dump f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Date of this level 0 dump: Tue Mar 27 14:32:47 2001. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Date of last level 0 dump: the epoch. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Dumping /vol/vol0/home/ to NDMP connec tion f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: mapping (Pass I)[regular files] f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: mapping (Pass II)[directories] f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: estimated 146499 KB. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: dumping (Pass III) [directories] f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:26:48 2001: Begin level 0 r estore f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:26:48 2001: Reading directo ries from the backup f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: dumping (Pass IV) [regular files] f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:26:48 2001: Creating files and directories. f820-rtp: LOG: RESTORE: f820-rtp: LOG: Warning: cannot create directory oracle: File exists f820-rtp: LOG: RESTORE: f820-rtp: LOG: Warning: cannot create directory test: Fi le exists f820-rtp: LOG: RESTORE: f820-rtp: LOG: Warning: cannot create directory dmj: Fil e exists f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:26:48 2001: Writing data to files. f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:27:08 2001: Restoring NT AC Ls. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: dumping (Pass V) [ACLs] f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: 146901 KB f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: DUMP IS DONE f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Deleting "/vol/vol0/../snapshot_for_ba ckup.1" snapshot. f820-rtp: LOG: RESTORE: f820-rtp: LOG: RESTORE IS DONE f820-rtp: HALT: The operation was successful! Waiting for f760cl1-rtp to halt too. The transfer was successful, but the source filer hasn't halted yet. Elapsed time: 0 hours, 0 minutes, 49 seconds. f760cl1-rtp: HALT: The operation was successful! The transfer is complete. Elapsed time: 0 hours, 0 minutes, 50 seconds. ------------------ now the incremental ------------------------- root@ultra5-rtp%[/usr/local/bin]>./ndmpcopy f760cl1-rtp:/vol/vol0/home f820-rtp: /vol/vol0/home -level 9 -dpass Source password: Destination password: Connecting to f760cl1-rtp. Connecting to f820-rtp. f760cl1-rtp: CONNECT: Connection established. f820-rtp: CONNECT: Connection established. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: creating "/vol/vol0/../snapshot_for_ba ckup.3" snapshot. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Using subtree dump f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Date of this level 9 dump: Tue Mar 27 14:41:38 2001. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Date of last level 0 dump: Tue Mar 27 14:38:20 2001. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Dumping /vol/vol0/home/ to NDMP connec tion f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: mapping (Pass I)[regular files] f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: mapping (Pass II)[directories] f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: estimated 10274 KB. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: dumping (Pass III) [directories] f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: dumping (Pass IV) [regular files] f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:35:38 2001: Begin increment al restore f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:35:39 2001: Reading directo ries from the backup f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:35:39 2001: Creating new fi les and directories. f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:35:39 2001: Writing data to files. f820-rtp: LOG: RESTORE: f820-rtp: LOG: Tue Mar 27 19:35:41 2001: Restoring NT AC Ls. f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: dumping (Pass V) [ACLs] f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: 10681 KB f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: DUMP IS DONE f760cl1-rtp: LOG: DUMP: f760cl1-rtp: LOG: Deleting "/vol/vol0/../snapshot_for_ba ckup.3" snapshot. f820-rtp: LOG: RESTORE: f820-rtp: LOG: RESTORE IS DONE f820-rtp: HALT: The operation was successful! Waiting for f760cl1-rtp to halt too. The transfer was successful, but the source filer hasn't halted yet. Elapsed time: 0 hours, 0 minutes, 45 seconds. f760cl1-rtp: HALT: The operation was successful! The transfer is complete. Elapsed time: 0 hours, 0 minutes, 46 seconds.

1 0

Re: Question on "vol copy"
by dmaloy＠atomaintl.com 24 May '01

24 May '01

Allen, The method that I have used in the past which I believe works better than vol copy is the tar command: mount both filesystems to your adminhost: mount tornado:/vol/users /tornado/vol/users mount tempest:/vol/vol0/users /tempest/vol/vol0/users cd to /tornado/vol/users and issue the tar command: tar -cf - . | (cd /tempest/vol/vol0/users ; tar -xvpf -) Doing this should also defrag the filesystems which I don't believe vol copy does...Someone can correct me here if I fell asleep during that part of the class. Don Maloy Intier Automotive Sr. CAD Administrator 19888 Haggerty Road Livonia, MI 48152 734.432.4418 "Allen, Pat" <pat(a)mbari.or To: "Toasters (E-mail)" <toasters(a)mathworks.com> g> cc: (bcc: Don Maloy/PDD/DORTEC) Subject: Question on "vol copy" 05/24/01 02:22 PM Hi all, I have an existing 740 (tornado) with two volumes - vol0 and users. I have a new 740 (tempest) with just vol0 and a qtree named "users". I want to copy all the user directories from torando:/vol/users to tempest:/vol/vol0/users in the easiest and quickest method possible. Both of the filers are connected via gig-ethernet to our main switch so using a filer-to-filer transfer would be the fastest. Do any of you know if the "vol copy" command can be used in this case. Can I specify that the destination is actually a qtree? The documentation for the vol command also says that the destination volume must be offline but that the root volume can't be taken offline. Is this a catch-22? Thanks for the help! --- Pat Allen (pat(a)mbari.org) Monterey Bay Aquarium Research Institute (MBARI) 7700 Sandholdt Rd, Moss Landing, CA 95039 (voice) 831-775-1724; (fax) 831-775-1620

2 1

RE: Question on "vol copy"
by Mohler, Jeff 24 May '01

24 May '01

'vol copy' can only be used to migrate data between two separate volumes, you cannot dump a remote volume into a Qtree. What you can do, is use ndmpcopy to migrate data from your remote users volume, to the local users Qtree. That would be as quick, or quicker in some cases than vol copy. Your last resort would be using cp with a unix host in the middle..or an NT solution to copy it all. The reason the destination volume cant be a root volume, is that you need the root volume to boot from..so therefore it cant be offline to be used as a vol copy or snapmirror destination volume. -----Original Message----- From: Allen, Pat [mailto:pat@mbari.org] Sent: Thursday, May 24, 2001 11:22 AM To: Toasters (E-mail) Subject: Question on "vol copy" Hi all, I have an existing 740 (tornado) with two volumes - vol0 and users. I have a new 740 (tempest) with just vol0 and a qtree named "users". I want to copy all the user directories from torando:/vol/users to tempest:/vol/vol0/users in the easiest and quickest method possible. Both of the filers are connected via gig-ethernet to our main switch so using a filer-to-filer transfer would be the fastest. Do any of you know if the "vol copy" command can be used in this case. Can I specify that the destination is actually a qtree? The documentation for the vol command also says that the destination volume must be offline but that the root volume can't be taken offline. Is this a catch-22? Thanks for the help! --- Pat Allen (pat(a)mbari.org) Monterey Bay Aquarium Research Institute (MBARI) 7700 Sandholdt Rd, Moss Landing, CA 95039 (voice) 831-775-1724; (fax) 831-775-1620

1 0

Support of SQL7 on filers pulled by MS?
by Lyons, Jim 24 May '01

24 May '01

MS KB article Q196904 "Support for Network Database Files," which used to detail the manner in which MS would support SQL7 on filers, has disappeared from the MS website. Does anyone know if MS has pulled support for this? Thought I would ask here before wading into MS support... Thanks, Jim

2 1

Question on "vol copy"
by Allen, Pat 24 May '01

24 May '01

Hi all, I have an existing 740 (tornado) with two volumes - vol0 and users. I have a new 740 (tempest) with just vol0 and a qtree named "users". I want to copy all the user directories from torando:/vol/users to tempest:/vol/vol0/users in the easiest and quickest method possible. Both of the filers are connected via gig-ethernet to our main switch so using a filer-to-filer transfer would be the fastest. Do any of you know if the "vol copy" command can be used in this case. Can I specify that the destination is actually a qtree? The documentation for the vol command also says that the destination volume must be offline but that the root volume can't be taken offline. Is this a catch-22? Thanks for the help! --- Pat Allen (pat(a)mbari.org) Monterey Bay Aquarium Research Institute (MBARI) 7700 Sandholdt Rd, Moss Landing, CA 95039 (voice) 831-775-1724; (fax) 831-775-1620

1 0

RE: Appending backups to tapes
by Fox, Adam 24 May '01

24 May '01

I guess I mis-read your question. To *not* append a backup, use a rewinding device. That will automatically rewind the tape at the end of the backup and then you're done. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: Chris Thompson [mailto:cet1@cus.cam.ac.uk] > Sent: Thursday, May 24, 2001 9:41 AM > To: john.f.mclaughlin(a)lmco.com > Cc: toasters(a)mathworks.com > Subject: Re: Appending backups to tapes > > > "John F. McLaughlin" <john.f.mclaughlin(a)lmco.com> writes > > > > I would like to know if it is possible not to append a backup to a > > previous backup tape. > > Possible *not* to append to a previous tape? Surely: take the > tape away > and lock it up in a safe where the filer can't work its evil ways with > it... :) > > Can you clarify what you mean here? Are you having some problem with > dumps being appended to a tape when you intended to use a new one? > Are you using basic dump/restore commands, or an NDMP > product, or what? > Manually loaded tape drive, or a stacker, or an all-singing > all-dancing > robot? etc. ... > > Chris Thompson University of Cambridge > Computing Service, > Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, > Phone: +44 1223 334715 United Kingdom. >

1 0

Appending backups to tapes
by John F. McLaughlin 24 May '01

24 May '01

I would like to know if it is possible not to append a backup to a previous backup tape.

2 1

RE: Appending backups to tapes
by Fox, Adam 24 May '01

24 May '01

It should be. It kind of depends on the software you are using. If you're just using our dump and mt commands on the filer, then just use non-rewinding tape devices and dump again. Then when you do finally rewind you can use mt to fast forward past a specific number of EOFs. Other backup software may have this feature built-in and I can't speak for most of them, but at least natively it's possible. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: John F. McLaughlin [mailto:john.f.mclaughlin@lmco.com] > Sent: Thursday, May 24, 2001 6:13 AM > To: toasters(a)mathworks.com > Subject: Appending backups to tapes > > > I would like to know if it is possible not to append a backup to a > previous > backup tape. >

1 0

RE: interface fun
by Fox, Adam 23 May '01

23 May '01

I need to retract this statement. I was working off of outdated info. This does *not* work. However, the on-board on the F840 does support VLAN tagging (which I think was another one of your questions). I researched this while I was verifying my first response. Sorry about that. Was working off of faulty memory cells. :) -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: Fox, Adam > Sent: Wednesday, May 23, 2001 5:22 PM > To: 'kevin graham'; toasters(a)mathworks.com > Subject: RE: interface fun > > > > > > Since I don't have the extra interfaces to play with, does > > anyone know if > > a VIF made up of vlan'able interfaces can also be vlaned? > > Rolling all of > > our interfaces into a VIF then VLAN'ing that would be > beautiful, but I > > don't want to go to the trouble having someone persue it if its not > > currently feasible. > > This is in fact true. You can create a big vif and then use vlan > tagging to get up to 4 vlans per vif. This requires at least ONTAP > 6.1. > > -- Adam Fox > NetApp Professional Services, NC > adamfox(a)netapp.com > >

1 0

NetApp F720 -- Password recovery
by Rafi Khardalian 23 May '01

23 May '01

Anyone know how to reset the password and configuration on an F720, without physically having the boot disks? In the past, I called NetApp support with the same problem, at which point I was given instructions on how to emulate a floppy boot. Unfortunately I misplaced this valuable piece of information. The only part I recall is setting a variable at the "ok"/bios prompt named something like ?floppy-boot?. Help would be greatly appreciated. Thanks. Rafi Khardalian Senior System Administrator Pennyweb, Inc.

2 1

RE: interface fun
by Fox, Adam 23 May '01

23 May '01

> > Since I don't have the extra interfaces to play with, does > anyone know if > a VIF made up of vlan'able interfaces can also be vlaned? > Rolling all of > our interfaces into a VIF then VLAN'ing that would be beautiful, but I > don't want to go to the trouble having someone persue it if its not > currently feasible. This is in fact true. You can create a big vif and then use vlan tagging to get up to 4 vlans per vif. This requires at least ONTAP 6.1. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com

1 0

Jump to page:

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