toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

RE: Backup a filer using Omniback
by Palinckx, Gregory 18 Jun '99

18 Jun '99

Hello Jan, In case you are not aware of it, there is a group within HP over in Germany that is working on the NDMP solution for OmniBack - Last update I received was late last year and they were shooting for a June 99 early release date. You might want to check with HP on the status - Let me know if your HP reps are unaware of the project and I'll see if I can track down a contact and/or the latest release date. To answer your question though, I know you can back up a filer with OmniBack over a NFS mount, but am not sure if it will back up a share or UNC path - if so, I would *suspect* that it will retain ACLs as well as UNIX permissions. Regards, Greg ----------------------------------------------------- Greg Palinckx Phone: 303.770.9158 System Engineer Mobile: 303.882.5996 Network Appliance Email: palinckx(a)netapp.com -----Original Message----- From: Schepers, Jan [mailto:Jan.Schepers@nl.origin-it.com] Sent: Friday, June 18, 1999 2:37 AM To: 'toasters(a)mathworks.com' Subject: Backup a filer using Omniback Hello people, it is very likely that there is somebody who has experience to backup a Netapp filer using HP/Omniback. Questions are: o is it possible ? o Is it possible to backup/restore both CIFS and UNIX meta data like ACL's ? o What about performance ? o What configuration (of the backup client) is required ? TIA, Jan Schepers =============== Origin - Sharing The Power Of Knowledge =============== Jan Schepers Building HCZ 4B.20 Computer Systems & Architectures Vonderweg 11 Origin/Technical Automation 5611 BK Eindhoven mailto:Jan.Schepers@nl.origin-it.com The Netherlands SERI schepers@nlorigin FAX :(+31-40-27)56171 Mobex :(+31-40-27)96025 Phone :(+31-40-27)57503 =======================================================================

1 0

Backup a filer using Omniback
by Schepers, Jan 18 Jun '99

18 Jun '99

Hello people, it is very likely that there is somebody who has experience to backup a Netapp filer using HP/Omniback. Questions are: o is it possible ? o Is it possible to backup/restore both CIFS and UNIX meta data like ACL's ? o What about performance ? o What configuration (of the backup client) is required ? TIA, Jan Schepers =============== Origin - Sharing The Power Of Knowledge =============== Jan Schepers Building HCZ 4B.20 Computer Systems & Architectures Vonderweg 11 Origin/Technical Automation 5611 BK Eindhoven mailto:Jan.Schepers@nl.origin-it.com The Netherlands SERI schepers@nlorigin FAX :(+31-40-27)56171 Mobex :(+31-40-27)96025 Phone :(+31-40-27)57503 =======================================================================

1 0

RE: Named Pipes?
by Muhlestein, Mark 18 Jun '99

18 Jun '99

Named pipes are used to communicate between software components. That would imply that there is some software loaded on the server which the DB application is talking to. Since we are not running NT on the filer, there is no way to do that. What you need to find out is if the DB supports running with the files on a remote drive, either using a mapped drive letter or UNC names. Many DB's (for example Oracle), do support that mode and can thus use the filer as back-end storage. Mark Muhlestein -- mmm(a)netapp.com -----Original Message----- From: Brian Shamblin [mailto:shamblin.brian@Mayo.EDU] Sent: Thursday, June 17, 1999 6:40 AM To: toasters(a)mathworks.com Subject: Named Pipes? We are trying to move our database files (not the database, just the data) from an NT server to our filer. The database application, DOCS Open from PC DOCS, insists on using Named Pipes to access the files (we're telling the application that they reside on NTFS). It appears that the filer has no support for this type of access method. Has anyone else encountered this problem? Any plans to add this support to ONTAP? Thanks in advance. ==================================================================== Brian Shamblin shamblin(a)mayo.edu Mayo Foundation voice: (507)284-4069 Rochester, MN fax: (507)284-9171 ====================================================================

2 1

Named Pipes?
by Brian Shamblin 18 Jun '99

18 Jun '99

We are trying to move our database files (not the database, just the data) from an NT server to our filer. The database application, DOCS Open from PC DOCS, insists on using Named Pipes to access the files (we're telling the application that they reside on NTFS). It appears that the filer has no support for this type of access method. Has anyone else encountered this problem? Any plans to add this support to ONTAP? Thanks in advance. ==================================================================== Brian Shamblin shamblin(a)mayo.edu Mayo Foundation voice: (507)284-4069 Rochester, MN fax: (507)284-9171 ====================================================================

2 1

Re: Virus
by yann.golanski＠ThePLAnet.net 17 Jun '99

17 Jun '99

Quoting Mark D Fowle <Fowle_Mark_D(a)CAT.com>: > Our NT Administrator wants to know how to protect the NetApps from viruses. > Unlike running on an NT server he > says he can't autoprotect data. Does anyone know how this might be done? Two ways. Use exim as a mail agent (yes, that DOES involve having a *nix box) and set a filter so that all attachemtn that match a list are `canned' or frozen. Then he can look thrugh them and only allow those he knows are not viruses. Of course, a list of known viruses can be set up to send the mail to /dev/null. The second: move to *nix. Check out VMware as a way to migrate. Remeber the filer is an appliance. It stores data. That's it. The security needs to come from somewhere else. -- Yann Golanski Internet Systems Developer yann.golanski(a)theplanet.net The Planet Online

1 0

RE: CIFS and the MaxMpxCt parameter
by Muhlestein, Mark 16 Jun '99

16 Jun '99

We have a fix for that in 5.3D14. The value is set via the cifs.max_mpx option, which has a maximum of 255, same as NT. Mark Muhlestein -- mmm(a)netapp.com -----Original Message----- From: Graham C. Knight [mailto:grahamk@ast.lmco.com] Sent: Wednesday, June 16, 1999 3:12 PM To: toasters(a)mathworks.com Subject: CIFS and the MaxMpxCt parameter We have a windows NT terminal server that servers out up to 60 Windows NT sessions at a time. The Windows NT people are complaining because after a certain amount of connections to our filer they start getting errors that look like this: "\\filername is not accessible. The remote procedure call failed and did not execute." So, they opened a call with Microsoft, and after 3 or 4 days of wrangling Microsoft has told them that the MaxMpxCt needs to be increased on the file server. Well, i can find no reference to this anywhere in NetApp's documentation, so i'm figuring that this is a Windows NT server thing and that it has nothing to do with a filer. But i don't know for sure, or if there is something else i can set that does the same type of thing. Here's the blurb from M$. Any ideas? Cause: During negotiation of the SMB dialect, the MaxMpxCt parameter (NT server registry, option in NetApp filer?) is passed to the client's (Terminal Server's) redirector where the limit of outstanding network requests is enforced. Explorer makes extensive use of directory notifications, resulting in a number of NTNotifyDirectoryChange SMBs being sent to the server (NetApp filer). This SMB request is classified as a long term request and is received by the server but not sent back until a change occurs. When several clients connect to the Terminal Server, the number of outstanding commands against the server can exceed the default maximum of 50. If this situation arises, other SMB requests will wait in the redirector until previous requests complete, timeout, or are cancelled. Resolution: Increase the MaxMpxCt parameter on the remote server to allow more simultaneous SMB connections. Thanks, Graham

1 0

CIFS and the MaxMpxCt parameter
by Graham C. Knight 16 Jun '99

16 Jun '99

We have a windows NT terminal server that servers out up to 60 Windows NT sessions at a time. The Windows NT people are complaining because after a certain amount of connections to our filer they start getting errors that look like this: "\\filername is not accessible. The remote procedure call failed and did not execute." So, they opened a call with Microsoft, and after 3 or 4 days of wrangling Microsoft has told them that the MaxMpxCt needs to be increased on the file server. Well, i can find no reference to this anywhere in NetApp's documentation, so i'm figuring that this is a Windows NT server thing and that it has nothing to do with a filer. But i don't know for sure, or if there is something else i can set that does the same type of thing. Here's the blurb from M$. Any ideas? Cause: During negotiation of the SMB dialect, the MaxMpxCt parameter (NT server registry, option in NetApp filer?) is passed to the client's (Terminal Server's) redirector where the limit of outstanding network requests is enforced. Explorer makes extensive use of directory notifications, resulting in a number of NTNotifyDirectoryChange SMBs being sent to the server (NetApp filer). This SMB request is classified as a long term request and is received by the server but not sent back until a change occurs. When several clients connect to the Terminal Server, the number of outstanding commands against the server can exceed the default maximum of 50. If this situation arises, other SMB requests will wait in the redirector until previous requests complete, timeout, or are cancelled. Resolution: Increase the MaxMpxCt parameter on the remote server to allow more simultaneous SMB connections. Thanks, Graham

1 0

Re: Data Ontap 5.3 and snapshots
by Jason D. Kelleher 16 Jun '99

16 Jun '99

In message <199906162020.NAA14794@tooting>, Guy Harris writes: >> >Has anyone fond a quick way to touch all CIFS shares and directories on >the >> >filer to convert the directories immediately to Unicode so all snapshots >> >thereafter are clean? >> >> From UNIX: >> >> find /filer_root -name .snapshot -prune -o -name SOMETHING_THAT_W >ONT_MATCH -print > >That works only if your UNIX box is a Linux box using "smbfs" to access >the filer (and I have the impression that may not work), or you have >some other UNIX client that uses CIFS rather than NFS. > >Otherwise, they'll be NFS accesses, which don't cause directory >conversion. NFS access triggers conversion with ONTAP 4.0 or later, unless I'm misreading the 5.3 docs. Check here: http://now.netapp.com/knowledge/docs/ontap/rel53/html/sag/multi12.htm Of course this could be wrong, wouldn't be the first error in the 5.3 documentation. BTW, when does NetApp plan on releasing non-ambiguous docs for second level virtual interfaces? jason

2 1

Re: Data Ontap 5.3 and snapshots
by Jason D. Kelleher 16 Jun '99

16 Jun '99

In message <000101beb7fa$c40f32f0$08ffa8c0(a)ossmball.rtp.opensystems.com>, "M ike Ball" writes: [...] >Has anyone fond a quick way to touch all CIFS shares and directories on the >filer to convert the directories immediately to Unicode so all snapshots >thereafter are clean? From UNIX: find /filer_root -name .snapshot -prune -o -name SOMETHING_THAT_WONT_MATCH -print From a Win box: Start file manager and do a search for "SOMETHING_THAT_WONT_MATCH" with the "Start From" being the root of the filer. That should do it. jason

2 1

Re: Virus
by Graham C. Knight 16 Jun '99

16 Jun '99

Mark D Fowle wrote: > > Our NT Administrator wants to know how to protect the NetApps from viruses. > Unlike running on an NT server he > says he can't autoprotect data. Does anyone know how this might be done? > > Mark Fowle > Caterpillar-BCP We run Mcafee virus scans on our filers nightly with very good results. We created a username in NT that maps to root on the filer and let it rip. Initially i was concerned with the mix of Unix and NT files on our volumes confusing the virus scanner, but after a lot of testing I'm satisfied that it's not a problem. GRaham

2 2

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