toasters June 2000

toasters@lists.teaparty.net

121 participants
153 discussions

NDMP Incremental backup issue
by Stephen Manley 09 Jun '00

09 Jun '00

Some of you may recall Matt Phelps encountering some trouble with NDMP incremental backups. We've identified the problem as bug 23356. The bug description will soon be available ONLINE at NOW. In a nutshell, the problem is this: An NDMP incremental dump will not include files with an mtime which is set to a time BEFORE the timestamp of the last level 0 dump, but created AFTER the timestamp of the last level 0 dump. Thus, your NDMP incremental backup may be missing some files that were created after the level 0 backup. The files that will be affected would primarily be: 1) Files that are restored, untar'ed through NFS, CIFS, or the native filer restore or NDMP restore. 2) Files that have has changed permissions, without the actual file changing (we won't back up the changed permissions). Note that the next level 0 backup WOULD include all of these files. The history of this bug: Some customers were encountering problems with various Windows applications using the Win32 API. Apparently, the ctime of an accessed file is updated by a large number of Windows apps (even if the file is only read) because the apps don't understand "last changed time". Thus, users with virus scanners would find that their incremental dumps included all files in the system... So we added a hidden option to NDMP and dump to ignore_ctime. (see online burt 17767 for more details on this issue) Unfortunately, all incremental NDMP backups incorrectly invoke that option as the default, and it cannot be overridden. The solution: We will soon have a 5.3.6 patch available that fixes this problem. This is also a good time to mention the NOW Bug Watcher utility. When we do a patch release that fixes this bug, those watching the bug will be automatically notified. (I'm guessing it probably works for other bugs, too. ;) http://now.netapp.com/cgi-bin/relfind?bugs=23356&rels= And thanks to Matt for being so helpful with this issue. Stephen Manley NDMP Spokesmodel

2 2

RE: Unix group permissiosn and NT access on a filer
by mark.muhlestein＠netapp.com 09 Jun '00

09 Jun '00

You want to turn on the cifs.perm_check_use_gid option. Thay way you will get normal UNIX group permission checking semantics. The entry in the security FAQ is intended to explain why that is not the default. Let us know if you still have problems. Mark > -----Original Message----- > From: Elizabeth Schwartz [mailto:eschwart@genuity.net] > Sent: Friday, June 09, 2000 12:55 PM > To: Muhlestein, Mark > Cc: eschwart(a)genuity.net; toasters(a)mathworks.com > Subject: RE: Unix group permissiosn and NT access on a filer > > > Thanks! > > IT sounds like what we need is a "cred-GID" am I reading this right? > > I want to give an NT user the right to access files from his > NT box that > members of his unix > group can access on the Unix side, on a filer set to unix file perms > > > At 11:21 AM 6/9/00 -0700, mark.muhlestein(a)netapp.com wrote: > >This is controlled via the option cifs.perm_check_use_gid. See > > > >http://now.netapp.com/NOW/knowledge/docs/olio/guides/53_troub > leshooting/faq > >.shtm > >l#anchor1392048 > > > >"My CIFS clients are seeing strange group access with > UNIX-style security > >files" > > > >Mark Muhlestein -- mmm(a)netapp.com > > > > > -----Original Message----- > > > From: Elizabeth Schwartz [mailto:eschwart@genuity.net] > > > Sent: Friday, June 09, 2000 8:19 AM > > > To: toasters(a)mathworks.com > > > Subject: Unix group permissiosn and NT access on a filer > > > > > > > > > Please forgive any NT terminology mangling, I'm a Unix person: > > > > > > We've got a filer that is set up as a Unix filesystem (as > opposed to > > > multiprotocol.) > > > Our NT users access their home directories as NT shares on > > > this filer. > > > Their NT login names match their Unix user id's. > > > > > > On the unix side, I created a group and made a > > > group-writeable directory > > > that is not readable to others. When the NT users log > into our unix > > > machine, they can write files in this directory. When they > > > access this > > > directory from the Unix side, only the owner can write files. > > > > > > Is this fixable? Without making dramatic changes to the > > > filer? (I do have > > > enough space to make a small extra partition if I really had to) > > > -- > > > Elizabeth Schwartz 781-262-6565 > > > Unix System Administrator eschwart(a)bbnplanet.com > > > Genuity, Inc > > > > > -- > Elizabeth Schwartz 781-262-6565 > Unix System Administrator eschwart(a)bbnplanet.com > Genuity, Inc >

1 0

RE: Unix group permissiosn and NT access on a filer
by Elizabeth Schwartz 09 Jun '00

09 Jun '00

Thanks! IT sounds like what we need is a "cred-GID" am I reading this right? I want to give an NT user the right to access files from his NT box that members of his unix group can access on the Unix side, on a filer set to unix file perms At 11:21 AM 6/9/00 -0700, mark.muhlestein(a)netapp.com wrote: >This is controlled via the option cifs.perm_check_use_gid. See > >http://now.netapp.com/NOW/knowledge/docs/olio/guides/53_troubleshooting/faq >.shtm >l#anchor1392048 > >"My CIFS clients are seeing strange group access with UNIX-style security >files" > >Mark Muhlestein -- mmm(a)netapp.com > > > -----Original Message----- > > From: Elizabeth Schwartz [mailto:eschwart@genuity.net] > > Sent: Friday, June 09, 2000 8:19 AM > > To: toasters(a)mathworks.com > > Subject: Unix group permissiosn and NT access on a filer > > > > > > Please forgive any NT terminology mangling, I'm a Unix person: > > > > We've got a filer that is set up as a Unix filesystem (as opposed to > > multiprotocol.) > > Our NT users access their home directories as NT shares on > > this filer. > > Their NT login names match their Unix user id's. > > > > On the unix side, I created a group and made a > > group-writeable directory > > that is not readable to others. When the NT users log into our unix > > machine, they can write files in this directory. When they > > access this > > directory from the Unix side, only the owner can write files. > > > > Is this fixable? Without making dramatic changes to the > > filer? (I do have > > enough space to make a small extra partition if I really had to) > > -- > > Elizabeth Schwartz 781-262-6565 > > Unix System Administrator eschwart(a)bbnplanet.com > > Genuity, Inc > > -- Elizabeth Schwartz 781-262-6565 Unix System Administrator eschwart(a)bbnplanet.com Genuity, Inc

1 0

RE: McAfee's Ghost
by jeff.mohler＠netapp.com 09 Jun '00

09 Jun '00

After more study internally, I was incorrect in my network based assumption. I have Emailed Ferdie back personally with this correction as well. http://now.netapp.com/NOW/cgi-bin/bol?Display=5408&Type=Detail is a link to our NOW site with specific details. :-----Original Message----- :From: Mohler, Jeff :Sent: Friday, June 09, 2000 10:07 AM :To: 'Ferdie Mazon'; toasters(a)mathworks.com :Subject: RE: McAfee's Ghost : : :Without any statistics to debug this..dunno what to say. : :Can you check ALL ethernet ports in question here? Sounds :like a blatant speed/duplex mismatch problem. : ::-----Original Message----- ::From: Ferdie Mazon [mailto:ferdie@san.rr.com] ::Sent: Friday, June 09, 2000 9:20 AM ::To: toasters(a)mathworks.com ::Subject: McAfee's Ghost :: :: ::Since moving the storage of Ghost images to the Filer, ::creating images has ::gone from .5 hours to just about 6 hours. I use a boot disk ::created from ::the network client program on Windows NT's administration tools. :: ::Does anyone else have this problem? :: ::Thanks, ::Ferdie Mazon :: :: :

1 0

RE: Unix group permissiosn and NT access on a filer
by mark.muhlestein＠netapp.com 09 Jun '00

09 Jun '00

This is controlled via the option cifs.perm_check_use_gid. See http://now.netapp.com/NOW/knowledge/docs/olio/guides/53_troubleshooting/faq… l#anchor1392048 "My CIFS clients are seeing strange group access with UNIX-style security files" Mark Muhlestein -- mmm(a)netapp.com > -----Original Message----- > From: Elizabeth Schwartz [mailto:eschwart@genuity.net] > Sent: Friday, June 09, 2000 8:19 AM > To: toasters(a)mathworks.com > Subject: Unix group permissiosn and NT access on a filer > > > Please forgive any NT terminology mangling, I'm a Unix person: > > We've got a filer that is set up as a Unix filesystem (as opposed to > multiprotocol.) > Our NT users access their home directories as NT shares on > this filer. > Their NT login names match their Unix user id's. > > On the unix side, I created a group and made a > group-writeable directory > that is not readable to others. When the NT users log into our unix > machine, they can write files in this directory. When they > access this > directory from the Unix side, only the owner can write files. > > Is this fixable? Without making dramatic changes to the > filer? (I do have > enough space to make a small extra partition if I really had to) > -- > Elizabeth Schwartz 781-262-6565 > Unix System Administrator eschwart(a)bbnplanet.com > Genuity, Inc >

1 0

RE: DLT 8000
by Uros Lampret 09 Jun '00

09 Jun '00

So there shouldn't be any problems with HP ShureStore DLT Autoloader 818 with Single-ended SCSI-2 fast/wide high density because for Filer I only found fast wide diferential. Is that compatible?

3 2

RE: McAfee's Ghost
by jeff.mohler＠netapp.com 09 Jun '00

09 Jun '00

Without any statistics to debug this..dunno what to say. Can you check ALL ethernet ports in question here? Sounds like a blatant speed/duplex mismatch problem. :-----Original Message----- :From: Ferdie Mazon [mailto:ferdie@san.rr.com] :Sent: Friday, June 09, 2000 9:20 AM :To: toasters(a)mathworks.com :Subject: McAfee's Ghost : : :Since moving the storage of Ghost images to the Filer, :creating images has :gone from .5 hours to just about 6 hours. I use a boot disk :created from :the network client program on Windows NT's administration tools. : :Does anyone else have this problem? : :Thanks, :Ferdie Mazon : :

1 0

RE: Creating a volume offline
by Caven, Marilyn 09 Jun '00

09 Jun '00

Great question Cliff. I have a similar situation where I am moving data from one filer to another and would very much like not to have to reboot. Secondly this data is exported and automounted by most of our workstations. I'd like to find a way to have the workstations give up the old mounts and mount the new ones without rebooting the workstations. Automount -v on the workstations does not release the old mount points. Any ideas? Marilyn Caven Unix Systems Administrator Next Level Communications Phone(707) 584-6302 -----Original Message----- From: Cliff Nadler [mailto:cnadler@colltech.com] Sent: Friday, June 09, 2000 5:19 AM To: toasters(a)mathworks.com Subject: Creating a volume offline I've looked through the docs, and I can't find how to create a volume so that it will be offline when created. I'm needing this to move some data from one set of disks on a filer to another using vol copy (where the target needs to be offline). And since this particular filer currently contains some database files and our common executable repository, I'm loathe to reboot it just to take a volume offline. Any ideas? -- -------------------------------------------------------------------------- Cliff Nadler Collective Technologies, Inc. (a Pencom Company) cnadler(a)colltech.com (617)-443-1144 -------------------------------------------------------------------------- To win, you must treat a pressure situation as an opportunity to succeed, not an opportunity to fail Gardner Dickinson

2 1

McAfee's Ghost
by Ferdie Mazon 09 Jun '00

09 Jun '00

Since moving the storage of Ghost images to the Filer, creating images has gone from .5 hours to just about 6 hours. I use a boot disk created from the network client program on Windows NT's administration tools. Does anyone else have this problem? Thanks, Ferdie Mazon

1 0

Unix group permissiosn and NT access on a filer
by Elizabeth Schwartz 09 Jun '00

09 Jun '00

Please forgive any NT terminology mangling, I'm a Unix person: We've got a filer that is set up as a Unix filesystem (as opposed to multiprotocol.) Our NT users access their home directories as NT shares on this filer. Their NT login names match their Unix user id's. On the unix side, I created a group and made a group-writeable directory that is not readable to others. When the NT users log into our unix machine, they can write files in this directory. When they access this directory from the Unix side, only the owner can write files. Is this fixable? Without making dramatic changes to the filer? (I do have enough space to make a small extra partition if I really had to) -- Elizabeth Schwartz 781-262-6565 Unix System Administrator eschwart(a)bbnplanet.com Genuity, Inc

1 0

← Newer
1
...
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 June 2000