Mount OES 11.2 nss-Volume on SLES11.3 via NFS

Hello I am newbie on this forum.
Have somebody mount a OES11.2-Nss-Vol on a SLES11.3 via NFS successfully?
I trying this since 3 days. without success.
Can somebody say, what parameter I need in /etc/exports and what I need into /etc/fstab?
that would be super
Thanks very much
Gene

Originally Posted by mrosen
Yeah, but.... This doesn't explain why you need yet another remote box
(runnign the same OS as the server where the NSS volume physically is)
to run the same webserver that already runs on the server that readily
has the NSS volume *right there*?
I can't speak for the OP. But for us its compartmentalization. That's why we do it. It makes cleaning up the most likely compromises significantly easier.
-- Bob

Similar Messages

Use OES2SP3 NSS Volume on a OES11SPx Server

Hello all
We have a couple of virtual OES2SP3 servers which we plan to replace with OES11SPx servers (on several remote sites).
Now we had the idea to mount the existing OES2SP3 NSS volume (own vmdk disk) with all the data on it to the new OES11SPx server.
With this procedure we would not need to migrate the data to the new server and would save some time.
Does anyone have experiences with such a action?
The NSS volume contains GW and a usual folder structure.
Thank you for your feedback and suggestions.
Best regards
Beat

Originally Posted by bschwegl
Hello all
We have a couple of virtual OES2SP3 servers which we plan to replace with OES11SPx servers (on several remote sites).
Now we had the idea to mount the existing OES2SP3 NSS volume (own vmdk disk) with all the data on it to the new OES11SPx server.
With this procedure we would not need to migrate the data to the new server and would save some time.
Does anyone have experiences with such a action?
The NSS volume contains GW and a usual folder structure.
Thank you for your feedback and suggestions.
Best regards
Beat
Works fine.
The gotcha's that I'm aware of:
When you power off the OES2 VM, and "remove the disk", and then you attach it to the OES11 VM, I don't believe it MOVES the actual VMDK file or directory structure.
In other words:
OES2 VM used DATASTORE1 and the directory was like \oes2-vm\oes2-vm.vmdk
OES11 would show it like:
DATASTORE1\oes2-vm\oes2-vm.vmdk
So if/when you decomission the OES2 box, you do NOT want to do a "delete from disk" as it will whack the vmdk and directory and your OES11 box will lose the volume.
I am unsure if a storage vmotion would work (if you have the paid VMware) or if you will have to power off the VM's and manually move the datastructures around. If going from esx host to esxi host, it can be time consuming.
If all the servers are using the one esxi host, then I imagine a simple rename, etc. would suffice (ie, power off the VM's, manually browse the datastore, change the directory name, or move it into the OES11 one, etc.)
But yes, what you want to do works and I've done it many times before.
Disconnect the disk from the OES2 box, reconnect it to the OES11 box, rescan for LUNs. I don't remember if a server reboot is needed, but I always like to do that. Otherwise I think you'll have to manually run nssmu to mount the volume, etc.
Obviously if it's Groupwise you'll need to adjust any config files if you used UNC paths for stuff, along with IP addresses (ie, change the IP of the POA/MTA, rebuild the databases, etc.)
--Kevin

How to list all directory quotas on an OES NSS Volume ??

Hi
I need to list all the directory quotas on an OES2 NSS volume, and haven't succeded yet!
I've tried to extract the info by inspecting /_admin/Manage_NSS/Volume/<volname>/DirInfo.xml, but it's always incomplete, as the file seems to have a 'fixed length' of 1024K.
Is there any way to:
a) completelly copy the file somewhere without the 1024K restriction
b) any other util that could do the job
Thanks!
IB

ibayarri,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

OES2SP3 to OES11SP1 nss volumes on iscsi target, hints?

Dear Colleagues,
I'm looking for a best migration scenario for the following assumtions:
One of SLES10SP3/OES2SP3 servers in my tree has file services and kanaka on it. Its nss volumes are located on iscsi targets attached from a Qnap storage. I'm migrating this server to a new hardware and SLES11/OES11SP1 and would like to transfer/switch volumes the easiest possible way. There is +/- 8TB of data to copy and I'm looking for a way around copynig it. Is it possible to perform the migration to newest SLES/OES on a different hardware and just re-attach iscsi target containing nss volumes, so all would stay consistent in the tree?
Please advise...

[QUOTE=mrosen;2266934]Hi.
On 06.06.2013 12:06, mpytel wrote:
> Is it possible to perform the migration to newest
> SLES/OES on a different hardware and just re-attach iscsi target
> containing nss volumes, so all would stay consistent in the tree?
Absolutely! You do a regular transfer ID migration, *without* copying
the NSS data that is on the iSCSI device. After the migration, bring up
the new server, attach to iSCSI, go into NSSMU and activate/mount the
partition once, and you're all set.
Dear Massimo,
I just finished TransferID migration and successfully re-attached iscsi targets containing NSS to the new server.
Is there an additional step I should execute to 're-read' volumes/pools contents so they appear on the new server?
M

Access NSS volumes from SLES

I am (finally!) getting ready to migrate from Netware 6.5 SP8 to OES 11 SP2. I've been going through the docs and I feel that I have most of the stuff figured out, but I couldn't find an answer to one question which is certainly easy enough for anybody who has experience with OES/Linux.
On my current Netware server I have some maintenance jobs run from cron which delete some files or copy files around (using utilities provided by TOOLBOX.NLM). In order to implement the same on OES/Linux, command line utilities that run on the 'base' SLES (cp, rm, ...) need to be able to access files on NSS volumes on the same server. Is this possible? Is it difficult? ;)

Originally Posted by vatson
need to be able to access files on NSS volumes on the same server. Is this possible? Is it difficult? ;)
They are all mounted under /media/nss/VOLUME_NAME/... possible and easy. There are all manner of every useful things that become super easy to do with shell script. Of course its also super easy to make mistakes in a way that would be more challenging without that level of access.
-- Bob

After Update, cannot delete files from nss volumes

Not sure if this is the same problem caused by the SLES11 upgrade, but after running all the upgrades on an OES11 system, I can see all the nss volumes of the upgraded servers from workstations using the Novell client, and I can copy or create files on these volumes. However, I cannot delete any files, they disappear from the workstation windows explorer when they are "deleted", but an f5 promptly shows the files are still there. I can go into the server as root, and delete the files under Linux with no problems, so this part is working OK.
I am running Novell 11.1 patch 1, and this problem has only been noticeable after the update installation.
I have supervisor rights to the volumes and files, and if I additionally set all the other file rights, I am still unable to delete the files.
Anyone got any ideas?
Cheers.
ChasR

Originally Posted by chas
Not sure if this is the same problem caused by the SLES11 upgrade, but after running all the upgrades on an OES11 system, I can see all the nss volumes of the upgraded servers from workstations using the Novell client, and I can copy or create files on these volumes. However, I cannot delete any files, they disappear from the workstation windows explorer when they are "deleted", but an f5 promptly shows the files are still there. I can go into the server as root, and delete the files under Linux with no problems, so this part is working OK.
I am running Novell 11.1 patch 1, and this problem has only been noticeable after the update installation.
I have supervisor rights to the volumes and files, and if I additionally set all the other file rights, I am still unable to delete the files.
Anyone got any ideas?
Cheers.
ChasR
I had a similar problem at updating with SP3 on SP4. It was similar, that permission ERASE is not applied to all trustees working through ncp in spite of the fact that it was available.
Has solved a problem that has redefined this permission for trustees on all catalogues.

Invalid descriptor error when trying to access nss volums

Hi everyone,
sorry for my english, when some users try to access shared nss volumes they get this error " invalid descriptor", but other folders are accessible at the same level.
users are on windows 7 and the last novell client.
thanks

On 23/06/2014 16:06, skaii wrote:
> sorry for my english, when some users try to access shared nss volumes
> they get this error " invalid descriptor", but other folders are
> accessible at the same level.
>
> users are on windows 7 and the last novell client.
Since you reference Novell Client I'm thinking that you're not using
Novell's Dynamic File Services product[1] which is what this forum is
for. If that is the case then you should repost in a more appropriate
forum, depending on whether you're using Open Enterprise Server (OES) or
NetWare.
HTH.
[1] http://www.novell.com/products/dynamic-file-services/
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

NSS Volume shows empty folders in a random manner

Hi there,
After expanding an NSS Volume, when brrowsing the volume, I can see randomly folders with files inside and folders which are empty.
Suse 11 SP2.
Any idea?
Thanks.

Originally Posted by smflood
On 26/11/2013 11:26, 6567410 wrote:
> After expanding an NSS Volume, when brrowsing the volume, I can see
> randomly folders with files inside and folders which are empty.
>
> Suse 11 SP2.
Since you've posted in a OES-related forum and reference NSS and "Suse
11 SP2" can I check which version of OES you're using. Please post the
output from "cat /etc/*release".
It would also be useful if you could confirm how up-to-date your server
is regarding patches.
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
Novell Open Enterprise server 11 (x86_64)
Version=11.1
Patchlevel=1

SBS and NSS Volumes

Hi,
I am fairly new to Novell, but I have recently been looking at Open
Enterprise Server and Linux Small Business Suite.
I really thought that Novell was making the best server solution yet for
small businesses, and thought that I could walk away from Windows SBS.
Open Enterprise Server does a great job, NSS volumes are easily added in
imanager, and iprint really does a great job at printing. However, it's
too expensive for a small business, and it doesn't come with groupwise as
standard.
I thought thats Linux Small Business Suite 9 would be perfect. I have just
installed it, and groupwise works well. Also creating users is easy.
But :- Why cant i simply add NSS volumes through imanager like I did on
OES? I thought that the ability to use Novell Volumes was one of the most
important things for a small business?
I am fairly new to this, so forgive me if it's just me! Any help is
appriciated. I have been looking at the feasibility of using Novell SBS
for small businesses that need; EMail/Printing/Volumes/Backups. Thought it
would be as easy to setup volumes as OES, and be simple to backup using
Tar or rsync.
Regards,
Luke.

> I appreciate what you have said. I think I have to keep with Novell SBS.
Thanks for the comments.
>
> I just assumed that Linux SBS would be a replacement of that, and as OES
> is based on Suse and offers NSS I just guessed it would be very easy for
> Novell to have included this in Linux SBS.
I did early on as well -- but my own read is that the Novell Small
Business team felt they really needed to do *something* to go with the
Linux flow at Novell -- not a bad thing. It is just that the timing
was such that an OES iteration wasn't something they could do. (Part of
what drives the Small Business team timing is Brainshare in Utah every
March).
At a guess, the next time round, we'll see an OES Small Business
product -- now that won't include BorderManager as that seems to be
only for the NetWare world, and folks can configure Linux based
firewalls, but it will include GroupWise.
>
> I have installed Microsoft SBS for clients, but find Novell's products
> more reliable, and I'm looking to offer these products.
>
Me too - I have three clients who pretty much must run Microsoft
servers, but for the rest, Novell is a much better fit.
As the world gets more 'fatigued' with Microsoft licensing and pricing
(both for applications and the OS), the market for Linux based
alternatives (both for applications and the OS -- including the server
OS) will be increasingly attractive -- and Novell is rather well
positioned for that.
I think one thing which might really drive the change will be solid
migration paths at the OS and application level. The current iteration
of Novell's Linux suite doesn't yet provide that (and really isn't
targeted there at this point). When it does, and folks can migrate
from NetWare or Microsoft Server, and from Win98/2k/xp to SuSE on the
desktop, and from Office to Open Office, AND from applications like
Quicken, Quickbooks, Act to Linux equivalents, I believe we'll see some
real movement in the small business marketplace. I honestly believe
that time will come -- and I for one very much need to get much more
Linux smart in preparation for that time.
Barry Schnur
Novell Support Connection Volunteer Sysop

NSS volume not visible

With NOWS 2.5 i have NSS installed and created DATA NSS
volume on second disc ( other than system )
Volume is activated, mounted, can be fully managed via iManager
or NRM, but admin or user logged via Novell Client ( 4.91 sp5 )
cannot see this volume. Volume SYS ( linux ext3 via NCP ) also not.
In eDirectory all OK - SYS, DATA, NSS admin object.
What is bad ?
Thanks for any tips.

May be Novell should setup a WIKI for SBS with option for public submission
of Tips or How-to (ofcourse this should be vetted before actually
publishing)
"KBOYLE" <[email protected]> wrote in message
news:[email protected]...
>
> toho;1931182 Wrote:
>> NCP is exactly for that: accessing your NCP volumes, it should
>> definitely work.
>> Do you see any messages in the system logfile? Any error message on the
>> client? Do you see the server and the tree in your network neighborhood?
>>
>> And Kevin,
>>
>> > NOWS SBE was designed to access NSS using Samba and not the Novell
>> Client
>>
>> Why not? I don-t see any hassles using NSS and the Novell client
>> together on an SBE-box and it-s a much easier setup (at least at the
>> server side) than messing around with all that Samba stuff. Create your
>> NSS volume(s), install the client on the workstation, assign rights, map
>> your folders and your set.
>> Especially for those coming over from NW this should be a lot easier to
>> handle than dealing with Samba.
>>
>>
>> Dirk
> I don't disagree Dirk. The target market for NOWS SBE are -new- small
> business customers with little or no Linux experience. If they are new
> customers, they probably don't have much Novell experience - NetWare or
> otherwise. Perhaps this is why so little emphasis is placed on the
> Novell Client.
>
> The standard scripted install is not very flexible. Samba is listed as
> a prerequisite to installing NSS and the documentation explains (IMO,
> poorly) how to access NSS files via Samba. My experience has been the
> more I deviate from the recommended configuration, the more likely I am
> to encounter issues.
>
> NOWS SBE is also the upgrade path from Novell SBS but there is precious
> little in the NOWS SBE documentation that discusses migration. There is
> little mention of the Novell Client other than a warning if you intend
> to deploy it to use the one supplied with NOWS SBE to minimize issues.
> So, how NOWS SBE is best deployed and managed would seem to depend a lot
> on whether or not you have any previous Novell experience and whether
> you are willing to deal with any issues you may encounter when deviating
> from the documented way of doing things.
>
>
> --
> Kevin Boyle
> ------------------------------------------------------------------------
> KBOYLE's Profile: http://forums.novell.com/member.php?userid=19359
> View this thread: http://forums.novell.com/showthread.php?t=401066
>

Prevent directory move on NSS volume

This issue has come up from time to time, but never annoying enough to address until now. I have a few directories on a OES 11 server running NSS volumes that are utilized as "public" folders for users and departments. The rights that are typically granted to the top-level directory are 'RWECMF' to the OU. The issue is that on occasion, a user will accidentally go mouse crazy and inadvertently move the directory to a new location, thus causing a search and find adventure to move the directory back to the proper location.
The question is, am I missing something really basic here to allow users to continue to perform what they need to do on the file system below public, but to prevent them from the ability to move the top-level directory, in this case "public?"
Any comments would be greatly appreciated.
Thanks!

On Wed, 28 Jan 2015 13:36:02 +0000, donaldsolberg wrote:
> This issue has come up from time to time, but never annoying enough to
> address until now. I have a few directories on a OES 11 server running
> NSS volumes that are utilized as "public" folders for users and
> departments. The rights that are typically granted to the top-level
> directory are 'RWECMF' to the OU. The issue is that on occasion, a user
> will accidentally go mouse crazy and inadvertently move the directory to
> a new location, thus causing a search and find adventure to move the
> directory back to the proper location.
Yup. It happens.
The usual answers are:
1. Take the rights away.
2. Shoot the offending users. Repeat until it stops happening.
3. Use something to "tune" the mouse action on the workstation to make
moving things accidently more difficult.
Pick one... But #2 is likely to lead to other problems.
> The question is, am I missing something really basic here to allow users
> to continue to perform what they need to do on the file system below
> public, but to prevent them from the ability to move the top-level
> directory, in this case "public?"
Sadly, no. If they have sufficient rights to do so, the server doesn't
know or care why they're moving stuff from "here" to "there". It's a
valid operation, and the server does what it does as quickly as possible.
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com
Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.

How to setup FTP to NSS Volume\directory

I need to setup an ID when it FTPs to the new OES2 server it will
automatically be in the NSS volume in the directory;
FS1\DATA:\Reports\FTPDATA
How do you do this with pure-ftp?
I setup an account (ftpuser) in edirectory and LUM enabled it to the
oes2 server but when i ftp in it ftps to the linux home directory
please help

For the migration tool:
There is a option for FTP migration, but I don't particularly recommend it. It doesn't do much. And what it does do, it doesn't do particularly well. On the positive side, getting what you had with NWFTPD out of OES "Novell FTP" is usually attainable now. But it requires getting your hands dirty and do a good review of pure-ftpd's abilities, settings, and methods.
The "Novell FTP" install pattern in OES Install & Config will lum enable pure-ftpd for you (via pam configuration), add some settings to the /etc/pure-ftpd/pure-ftpd.conf file for OES specific enhancements, and a few other things like that.
The migration tool does one thing: It looks at a small number of setting in NetWare's sys:/etc/ftpserv.cfg and sets corresponding values in /etc/pure-ftpd/pure-ftpd.conf. But there are many settings unique to each, which don't translate. And the migration tool doesn't do all that it could, and it does some things it shouldn't:
- It doesn't turn on all the remote server / ftp gateway / NCP home directory features that you're used to be always on in NWFTPD. In pure-ftpd, you have to turn those on yourself (in pure-ftpd.conf), as they are off by default. As these features are now optional, it was decided to have them default to being off. This keeps ftp server code paths much simpler for those who don't need those features.
- It tends to remove some settings from pure-ftpd.conf if they are set to the defaults. While that won't have any negative impact on functionality, it is annoying for people who like to all the settings in the file, either as examples or to remind them of the current values. If you want to accomplish what the migration tool does without risking those deletions, I recommend you see table 25-1 at the following link. That shows what setting from NetWare are carried into pure-ftpd.conf during the migration process. You can usually do it manually in just a few minutes.
Novell Documentation
And as Ketter indicated in another reply, the OES 11 online doc holds information that will help. Much of the FTP home directory features were added or enhanced in OES 11 SP1, so be sure to use the current doc.

Rsync not copying NSS volumes

I have two OES 11 servers. Trying to rsync between NSS volumes. I
run this command on the source server:
rsync -av /media/nss/VOL1/PROJECTS/* 192.168.1.39:projects
It prompts me for the password. I enter the password and it appears
to be copying files. But nothing shows up on the destination server.
Is there something special about OES or NSS volumes that I have to set
to get this to work?
Thanks,
Ken

Originally Posted by ketter
On Wed, 30 May 2012 22:46:01 GMT, ataubman
<[email protected]> wrote:
>
>Good, that'll save me mentioning that you've posted in a NetWare forum,
>not OES!
LOL! Yesterday was one of those days! Not quite a Monday, but still.
I saw OES and didn't read the rest of the line in my newsreader.
Thanks for not pointing out my mistake in front of the whole class.
Ken
Can you tell me where I can download a copy of rsync for netware 6.5?

Useed percent email alert on NSS volumes

I was wondering if there is a way to setup OES to send email alerts when a drive gets to a specified % free in space?
Sincerely,
Ken

mdallair wrote:
>
> kheinz;2343040 Wrote:
>> I was wondering if there is a way to setup OES to send email alerts when
>> a drive gets to a specified % free in space?
> OES11 Sp2 already include a built-in nagios so it's possible to
> configure it to do what you need.
The plugin check_disk of nagios does not have an option to check NSS
volumes only. To I simply exclude all other types in order to just get NSS:
# 'check_local_disk_nssvol' command definition
define command{
command_name check_local_disk_nssvol
command_line sudo /usr/lib/nagios/plugins/check_disk -w
$ARG1$ -c $ARG2$ -X nsspool -X xfs -X debugfs -X proc -X sysfs -X tmpfs
-X devpts -X
ext2 -X ext3 -X ext4 -X btrfs -X reiserfs -X fusectl -X securityfs -X
adminfs -X binfmt_misc -X proc -X nssadmin -X novfs
See any documentation on Nagios on how to send email alerts upon
specific events.
Günther

Migrating Users Quotas on NSS Volumes

Hi !
We have a Netware 6.5 SP7 server with around 45000 users on it. We have a NSS volumes called USERS where must of the users have a quotas restrictions.
How can I migrate all the users quotas restrictions from a Netware server to an OES 2 Linux server ?
I tried many tools like SCMT, migfiles, tcnvlnx.nlm, ... Everything is migrating correctly EXCEPT the users quotas on the NSS volumes.
Any ideas ?
Eric

Marcel Cox wrote:
> Are your users lum enabled?
Quotas don't need LUM enabled users on OES2 Linux.
But if Eric is referring to Volume Space Restrictions and migrations
just folders, then it won't work.. directory restrictions should
migrate, haven't tried becoz we only user Volume based.
6.1.3 User Space Restrictions Only Migrated in Full Volume Copies
In consolidation projects where individual folders are dragged and
dropped, or where a volume is
copied to a folder on the destination server, user space restrictions on
the source volume are not
migrated to the destination volume.
If your consolidation project is set up to copy an entire volume, with
the contents of the source
volume being copied to the root of the destination volume, user space
restrictions are migrated to the
destination volume. If user space restrictions already exist on the
destination volume, they are
overwritten with the restrictions migrated from the source volume.
-sk

Mount OES 11.2 nss-Volume on SLES11.3 via NFS

Similar Messages

Maybe you are looking for