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

Similar Messages

Public_html on NSS Volume

The Apache2 in the OES2 SP2 includes the mod_userdir, so public_html directories in a Linux-Users(!) homedir, f. e. under /home/user1 are working fine.
so my problem is now, how to move this to my users homedirs on the nss volume?
have the users to be lum enabled?
Thank yOu

Originally Posted by TFe
- Apache setup:
The browser URL for the home directory users will be http://server-ip-address/~username
Create a .conf file with the directives below under /etc/apache2/conf.d - it could be named "HomeDir.conf" for example.
This example uses the "UserDir" directive to set the path and directory for all of the home directory users. It is where you choose to put the user's home directory that exists on an NSS volume of the same server.
The asterisk ( * ) symbol is a place holder for any home user in that NSS volume path.
Restart apache when changes are made to the .conf file, using the command "rcapache2 restart"
UserDir /media/nss/VOL1/data/*/docs
<Directory "/media/nss/VOL1/data/*/docs">
Options Indexes Multiviews
AllowOverride None
Order deny,allow
Allow from all
</Directory>
From Configuring User Home Directories on Linux using an NSS volume on the same server.
Cheers

Access forbidden when Apache is trying to use NSS volume

I'm helping a customer migrate from an OES2 SBE server to an OES2 Linux server running under VMware. The new server is up and seems to be running fine and I've migrated all of the data over, but not using the Migration Tools as I could not get them to work. (That's another thread in the forums. Could that problem be related to this problem???).
Anyway, on their old server they run Apache for their public web site and it's default directory is on an NSS volume. It's configured in default-server.conf and it works fine. There are no virtual servers configured in Apache
On the new server, I've duplicated every setting I can find in Apache and every permission in the file system to match exactly with the old server. However, all I can get from Apache is an "Error 403: You don't have permission to access the requested directory. There is either no index document or the directory is read-protected."
If I move the web folder off of the NSS volume and adjust default-server.conf, it serves the pages up just fine. So, I'm pretty sure it's NSS permissions related. The wwwrun user and www group are pre-existing in the Tree and the old server is using them and they appear to be LUM enabled. There's a Unix Workstation object in the tree for the new server, so I'm assuming it's LUM enabled. From what very little I understand about LUM, it appears to be working but I wouldn't bet much on that. I also tried configuring Apache to use a virtual host instead of the default-server and that didn't help either.
I've found several other threads and TIDS on the topic and tried them all but nothing worked. I'm at the end of my knowledge!
-Farren

farren wrote:
>
> I'm helping a customer migrate from an OES2 SBE server to an OES2 Linux
> server running under VMware. The new server is up and seems to be
> running fine and I've migrated all of the data over, but not using the
> Migration Tools as I could not get them to work. (That's another thread
> in the forums. Could that problem be related to this problem???).
>
> Anyway, on their old server they run Apache for their public web site
> and it's default directory is on an NSS volume. It's configured in
> default-server.conf and it works fine. There are no virtual servers
> configured in Apache
>
> On the new server, I've duplicated every setting I can find in Apache
> and every permission in the file system to match exactly with the old
> server. However, all I can get from Apache is an "Error 403: You don't
> have permission to access the requested directory. There is either no
> index document or the directory is read-protected."
>
> If I move the web folder off of the NSS volume and adjust
> default-server.conf, it serves the pages up just fine. So, I'm pretty
> sure it's NSS permissions related. The wwwrun user and www group are
> pre-existing in the Tree and the old server is using them and they
> appear to be LUM enabled. There's a Unix Workstation object in the tree
> for the new server, so I'm assuming it's LUM enabled. From what very
> little I understand about LUM, it appears to be working but I wouldn't
> bet much on that. I also tried configuring Apache to use a virtual host
> instead of the default-server and that didn't help either.
>
> I've found several other threads and TIDS on the topic and tried them
> all but nothing worked. I'm at the end of my knowledge!
>
> -Farren
>
>
Did you give rights to wwwrun to the volume?

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

Not enough space on nss-volume

Hello,
system: 3node sles10.3 + oes2sp3
nss-volume
Some of our users (Windows 7 + NC Client) report that they want to copy some files to their nss-share, it says not enough space.
The same when we wanted to copy files from the linux-console (cp) -> not enough space on device.
We definitely have enough space on the volume and there are also no quotas set.
Can anyone help?
thx,
hugo

Originally Posted by susehoush
Hello,
system: 3node sles10.3 + oes2sp3
nss-volume
Some of our users (Windows 7 + NC Client) report that they want to copy some files to their nss-share, it says not enough space.
The same when we wanted to copy files from the linux-console (cp) -> not enough space on device.
We definitely have enough space on the volume and there are also no quotas set.
Can anyone help?
thx,
hugo
Some users? So others can write to that volume?
If not, have you maybe set a volume space restriction in nssmu on the properties of the volume? & what's the output of the console command 'df -h' and 'nsscon /spaceinfo'?
Cheers,
Willem

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

How can i use the ssl code of mozilla nss to visit a https server.

i want to use the mozilla nss source code to make a client program. how can i do it? the clent is used to visit a https server. but i couldn't find the code about how to do it. i just found that there is code about the clent / server using tcp/ip, but not about browser/server.

I am a c programer. Our goal is to communication with our https server.
I steped using "https://developer.mozilla.org/en-US/docs/NSS/tools/NSS_Tools_ssltap" but it did'nt work successfully.
It looks like the image's shows even I used the browser to visit the web site steped. Could you tell me the detail.

Server umounts NSS volumes for no obvious reason

OES2 SP1, 2-node cluster
I had a server unmount an NSS volume with the message below in the logs.
Any ideas what could have caused this?
SAN_SERVER is the cluster pool.
USERAREA is an NSS volume in the pool.
Code:
May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER.monitor failed 256
May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER 1 failures in last 600 seconds
May 21 10:21:25 vishnu adminus daemon: umounting volume USERAREA lazy=1
May 21 10:21:25 vishnu adminus daemon: Failed to delete the directory /media/nss/USERAREA. Error=39(Directory not empty)
May 21 10:21:25 vishnu adminus daemon: Entries for Volume USERAREA from pool SAN are not removed during pool deactivation
May 21 10:21:25 vishnu kernel: Waiting for 2 Inuse beasts to unlink
... repeated multiple times
May 21 10:21:36 vishnu kernel: fastReadCache - Buffer's should always have an inode
May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
... repeated multiple times

This looks as if you have a monitor script that is looking at your
resource - spots a failure and then starts a unload/load routine.
I think that your cluster monitor script has been copied from another
resource and has not been edited to reflect the change
T
On Tue, 22 May 2012 09:46:01 GMT, vimalkumar v
<[email protected]> wrote:
>
>*OES2 SP1, 2-node cluster
>*
>I had a server unmount an NSS volume with the message below in the
>logs.
>Any ideas what could have caused this?
>
>SAN_SERVER is the cluster pool.
>USERAREA is an NSS volume in the pool.
>
>
>Code:
>--------------------
> May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER.monitor failed 256
> May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER 1 failures in last 600 seconds
> May 21 10:21:25 vishnu adminus daemon: umounting volume USERAREA lazy=1
> May 21 10:21:25 vishnu adminus daemon: Failed to delete the directory /media/nss/USERAREA. Error=39(Directory not empty)
> May 21 10:21:25 vishnu adminus daemon: Entries for Volume USERAREA from pool SAN are not removed during pool deactivation
> May 21 10:21:25 vishnu kernel: Waiting for 2 Inuse beasts to unlink
> ... repeated multiple times
> May 21 10:21:36 vishnu kernel: fastReadCache - Buffer's should always have an inode
> May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
> May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
> ... repeated multiple times
>--------------------

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

Antivirus: clustered NSS-Volume

hi,
I'm not sure if this is the right forum, but...
we want to install Antivirus-Services (sophos) on our cluster-nodes to protect against viruses on the nss-volume.
1. Does anyone have any experience on this subject - especially on the question if it's a good idea to run the AV on the cluster-nodes (load, locking of files, behaviour on virus detection and so on.)?
2. What is the Novell-recommended way to deal with the AV-Question in a clustered environment (sles10sp3+ oes2sp3)?
would appreciate any help on this.
thx,
hugo

Am 06.07.2011 17:36, schrieb susehoush:
> we want to install Antivirus-Services (sophos) on our cluster-nodes to
> protect against viruses on the nss-volume.
>
> 1. Does anyone have any experience on this subject - especially on the
> question if it's a good idea to run the AV on the cluster-nodes (load,
> locking of files, behaviour on virus detection and so on.)?
A volume mounted as nssvol on an OES2 SP2,3 server might be scanned with
savscan like a local one. We use an entry to /etc/cron.d which is
created by the cluster load and deleted by the cluster unload script.
Cron starts a daily savscan on the cluster volume, eg:
savscan /media/nss/VOL1 -exclude $EXCL -p=$SLOGDIR/sophos-$2-$DATE
-move=$QUARANTINE --no-follow-symlinks --no-reset-atime -archive -all
-pua -nc -mime -oe
Replace the variables with suitable names. Be aware that the "-archive"
and "-all" options might slow down the scan significantly.
A savscan job will result in 100% CPU load. With todays multicore CPU
this should be OK provided that not too many are started at once. I
should add a nice statement to the call also.
Savscan interferes with our backup system. I had to add the
"--no-reset-atime" option. Without it the ctime of all files scanned
will be updated which results in the files being included in the next
incremental backup. This turns all incremental backups in full ones, of
course.
I never tried on access scanning. IMO this does not make much sense on a
file server and should be done on the clients.
> 2. What is the Novell-recommended way to deal with the AV-Question in
> a clustered environment (sles10sp3+ oes2sp3)?
I have no idea. But in general support at sophos is quite responsive.
Gnther

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.

Commvault issue with JobResults on NSS volume

Hi all, we see an issue with Commvault 9R2 (sp10) using a Linux i-data agent client on OES2SP3 x64 backing up (clustered) NSS volumes. For speed we, this case, do not want to use a NSS i-data agent, so we just leverage the Linux i-data agent.
The issue is that if we use the Linux i-data agent and the jobresults directory is also hosted on the same NSS volume that's being backed up we get an error on failures.cvf
"Could not open failures file [/media/nss/LBAPOA/galaxy/JobResults/2/268/Failures.cvf] error number [19, No such device]. The backup would continue but this would affect the ability of reattempting the failed file backup during next incremental backup. A full backup is recommended to back up all files. Check the following: 1. The account this product uses has permissions to the product's install directory. 2. Sufficient disk space is available for the Job Results directory. If the problem persists, please upload log files from CommServe, MediaAgent and Client and contact your vendor's support hotline with the job ID of the failed job."
If we (for testing only) move only the jobresult directory to an ext3 volume we do not see the issue.
Has someone seen (and hopefully fixed) this issue before? My guess it's a Commvault issue, but just before we open a SR with them I would like to now if there's a good guess to solve this:)

sveld,
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/

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

Safely point an NSS VMDK to the new server during transferID

I have two VMWare VMDK NSS Volumes hosted on an iSCSI array for a class, connected to my existing OES2SP3 server. I'm installing a transfer ID server instance OES11SP2 I'd like to to migrate the "locally" hosted vmdk NSS volume over to the new server. (I don't have space to migrate the other two huge volumes.)
So I'm going to install the transfer id server and migrate the main STORAGE volume to it and then remove the two VMDKs from the OES2SP3 VM and install them onto the new OES11SP2 VM. I assume that I do this move after I finish the transfer ID from the old VM to the new VM.
My question I'm hoping to have answered is -> If you move an NSS VMDK to a server after the transfer ID occurs, will the new server have to have the existing NSS edir objects changed in any way or will it simply assume ownership of them when they are mounted at boot? Is it safe to move them after the transfer id or must I do it before. I didn't like the idea of yanking the two NSS volumes out from the old server prior to doing to transfer id.
Thanks,
-Nyle

Originally Posted by nlandas
I have two VMWare VMDK NSS Volumes hosted on an iSCSI array for a class, connected to my existing OES2SP3 server. I'm installing a transfer ID server instance OES11SP2 I'd like to to migrate the "locally" hosted vmdk NSS volume over to the new server. (I don't have space to migrate the other two huge volumes.)
So I'm going to install the transfer id server and migrate the main STORAGE volume to it and then remove the two VMDKs from the OES2SP3 VM and install them onto the new OES11SP2 VM. I assume that I do this move after I finish the transfer ID from the old VM to the new VM.
My question I'm hoping to have answered is -> If you move an NSS VMDK to a server after the transfer ID occurs, will the new server have to have the existing NSS edir objects changed in any way or will it simply assume ownership of them when they are mounted at boot? Is it safe to move them after the transfer id or must I do it before. I didn't like the idea of yanking the two NSS volumes out from the old server prior to doing to transfer id.
Thanks,
-Nyle
IF my memory serves (this was a while ago), we did it that way (leave the "old" disk attached). Transfer ID, power off both servers, disconnect "old" disk and reconnect to "new" server. Power up and I think it just worked. I don't recall having to re-run anything in nssmu.
But again, that WAS a while ago.

Use OES2SP3 NSS Volume on a OES11SPx Server

Similar Messages

Maybe you are looking for