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

Similar Messages

OES11 SP2 - Linux File System and NSS Pools & Volumes

Planning to install our first OES11 SP2 server into an existing tree - the
idea is to run this new OES11 server virtualized on VMware ESXi 5.5
The existing tree has two physical NW6.5SP8 servers running eDirectory
Version 8.7.3.10b (NDS Version 10554.64). One of the existing Netware
servers is used for DHCP/DNS, File Sharing from three NSS volumes and
Groupwise 7.0.4 whilst the second server is used for FTP services and
eDirectory redundancy. Ultimately the plan is to have two virtualized OES11
SP2 server with one for file sharing and the other for making the move from
GW7 to GW2012. And we're planning to stick with NSS for file sharing on the
new OES11 SP2 server.
I've come across a couple of posts for earlier versions of OES which
recommended not to put the Linux Native OS File System and NSS storage
pools/volumes on the same hard drive. Apparently the advice was a result of
needing to allow EVMS to manage the drive which could be problemmatic.
I've read the OES11 documentation which says that "The Enterprise Volume
Management System (EVMS) has been deprecated in SLES 11, and is also
deprecated in OES 11. Novell Linux Volume Manager (NLVM) replaces EVMS for
managing NetWare partitions under Novell Storage Services (NSS) pools."
So I'm wondering if there is still a compelling requirement to keep the
Linux Native File System and NSS pools/volumes on separate hard drives or
can they both now safely co-exist on the same drive without causing
headaches or gotchas for the future?
Neil

Hi Willem,
Many thanks for the further reply.
So we can just use the VMWare setup to "split" the one physical drive into
two virtual drives (one for the OS and the second for the pools).
And I've seen posts in other forums about the need for a decent battery
backed cache module for the P410i controller so I'll make sure we get one
(probably 512Mb module + battery).
Can I ask what is the advantage of configuring each VM's virtual disk to run
on it's own virtual SCSI adapter (by setting disk1 to scsi 0:0, disk2 to
scsi 1:0, and so on)?
Cheers,
Neil
>>> On 9/5/14 at 12:56, in message
<[email protected]>,
magic31<[email protected]> wrote:
> HI Niel,
>
> xyzl;2318555 Wrote: >
>> The new installation will run on a Proliant ML350 G6 with P410i>
> controller
>> so we can use the raid capability to create two different logical drives>
> as
>> suggested.
>
> As you will be using ESXi 5.5 as host OS, it's not needed to split
> thehost server storage into two logical drives... unless that's what
> youwant in perspective for "general performance" or redundancy reasons.
> Italso depends on the options that P410i controller has.
>
> On a side note, I'm not too familiar with the P410i controller... domake
> sure you have a decent battery backed cache module installed, asthat will
> greatly help with the disk performance bit.
> If the controller can handle it and the controller can handle it, go
> forraid 10 or raid 50. That might be too big a space penalty but will
> helpwith disk performance.
>
> Once you have your VMware server up and running, you can configure
> thetwo VM's with each two or more drives attached (on for the OS,
> thesecond or others for your pools).
> I usually create a virtual disk per pool+volume set (e.g. DATAPOOL
> &DATAVOLUME on one vm virtual disk, USERPOOL & USER volume on an other
> vmvirtual disk).
> With VMware you can than also configure each VM's virtual disk to run
> onit's own virtual SCSI adapter (bij setting disk1 to scsi 0:0, disk2
> toscsi 1:0, and so on).
>
>
> xyzl;2318555 Wrote: > Do you have any suggestions for the disk space that
> should be reserved> or
>> used for the Linux Native OS File System (/boot, /swap and LVM)?
>>
>
> Here's one thread that might be of interest (there are more
> throughoutthe SLES/OES
>
forums):https://forums.novell.com/showthread...rtitioning-%28
> moving-from-NW%29
>
> I still contently follow the method I choose for back in 2008, justwith
> a little bigger sizing which now is:
>
> On a virtual disk sized 39GB:
>
> primary partition 1: 500 MB /boot , fs type ext2
> primary partition 2: 12GB / (root), fs type ext3
> primary partition 3: 3 GB swap , type swap
>
> primary partition 4: LVM VG-SYSTEM (LVM partition type 8E), takes up
> therest of the disk **
> LVM volume (lv_var): 12 GB /var , fs type ext3
> LVM volume (lv_usr-install): 7GB /usr/install, fs type ext3
> * there's still a little space left in the LVM VG, in case var needs
> toquickly be enlarged
>
> One thing that's different in here vs what I used to do: I replaced
> the/tmp mountpoint with /usr/install
>
> In /usr/install, I place all relevant install files/IOS's
> andinstallation specifics (text files) for the server in question. Keeps
> itall in one neat place imo.
>
> Cheers,
> Willem-- Knowledge Partner (voluntary sysop)
> ---
> If you find a post helpful and are logged into the web interface,
> please show your appreciation and click on the star below it.
>
Thanks!---------------------------------------------------------------------
---magi
> c31's Profile: https://forums.novell.com/member.php?userid=2303View this
> thread: https://forums.novell.com/showthread.php?t=476852

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
>

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.

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?

Strange directory behaviour on NSS volume OES11 SP1

Hi All,
A couple of months ago we installed an OES11 SP1 server with an NSS volume (VOL1:) for all our installation files.
In the root of the VOL1: volume, we created a directory named _Install (yes, underscore)
In this directory we created a lot of subdirectories with installation files for several applications, to keep things short, let's say DIR-A, DIR-B, DIR-C DIR-D DIR-E etc.
So if we opened VOL1:, we just saw the _Install direcory in the root of VOL1:, and if we opened the _Install directory, we saw the DIR-A, DIR-B etc.
But today, we opened the VOL1:, saw, the _Install directory, but also the DIR-A, DIR-B, DIR-C etc. in the folowing manner:
_Install (normal)
_Install\DIR-A
_Install\DIR-B
_Install\DIR-C
etc.
If we doubleclick on one of the directories in the root of VOL1:, we actually open the directory below the _Install directory. It's just like we have a kind of symbolic links, or shortcut's to the real directories in our root.
Never seen this before.
Anybody a clue for this?
regards,
Mark

On 29/10/2013 14:46, MarkHofland wrote:
> A couple of months ago we installed an OES11 SP1 server with an NSS
> volume (VOL1:) for all our installation files.
> In the root of the VOL1: volume, we created a directory named _Install
> (yes, underscore)
> In this directory we created a lot of subdirectories with installation
> files for several applications, to keep things short, let's say DIR-A,
> DIR-B, DIR-C DIR-D DIR-E etc.
> So if we opened VOL1:, we just saw the _Install direcory in the root of
> VOL1:, and if we opened the _Install directory, we saw the DIR-A, DIR-B
> etc.
>
> But today, we opened the VOL1:, saw, the _Install directory, but also
> the DIR-A, DIR-B, DIR-C etc. in the folowing manner:
>
> _Install (normal)
>
> _Install\DIR-A
> _Install\DIR-B
> _Install\DIR-C
>
> etc.
>
> If we doubleclick on one of the directories in the root of VOL1:, we
> actually open the directory below the _Install directory. It's just like
> we have a kind of symbolic links, or shortcut's to the real directories
> in our root.
>
> Never seen this before.
>
> Anybody a clue for this?
Having seen your other replies, you're opening VOL1: in Windows Explorer?
What do you see if you do a DIR from a Command Prompt window?
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.

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/

Vibe file repository on NSS volume?

Has anyone figured out how to set up Vibe to use a file repository on an NSS volume? Or how to change to file repository location post install?
I made the mistake of specifying /media/nss/VOL1/teaming as my file repository during the initial installation and now either need to change the location or make it work as is.
I'd be willing to remove Vibe completely and start again if someone knows a way to proceed with that.

We moved our content from a local disk to the NAS. I'm looking at my notes, here are the steps we used:
- Setup NAS share and copied archivestore and filerepository folders from current repository to NAS share.
- Gave the user teaming was setup as full rights to the files (we are using Linux) and change ownership to match if needed.
- Run the installer and choose reconfigure. In my notes I have written to modify the path to the repository in the install.xml file. I'm not sure if that was a necessary step.
- Do a full re-index.
I'm not sure if this is the best or most efficient way to do it, but it worked for us.
Tom

LVM and NSS in OES11

I am building out a replacement server which will be the target for a server migration. The server will host an NSS volume. In the past I have always created an array-level logical drive for my NSS partiton/volume. Rather than doing this, I would rather just have one logical drive and partition the space using LVM (except for /boot and swap). Once I create the LVM and add /, /home, /var, /tmp to it, I will have a lot of extra space which I want to use for the NSS volume.
So, is it possible to use the unused space in LVM for NSS? Or should I stick which a separate logical partition for NSS?
Chris

Originally Posted by cmosentine
I am building out a replacement server which will be the target for a server migration. The server will host an NSS volume. In the past I have always created an array-level logical drive for my NSS partiton/volume. Rather than doing this, I would rather just have one logical drive and partition the space using LVM (except for /boot and swap). Once I create the LVM and add /, /home, /var, /tmp to it, I will have a lot of extra space which I want to use for the NSS volume.
So, is it possible to use the unused space in LVM for NSS? Or should I stick which a separate logical partition for NSS?
Chris
With OES11 it's possible and quite easy to use the left free space on the system disk for NSS.
It also does not have the potential for havoc as was the case with OES2 (as with OES2 this was also possible, it just meant using EVMS on the system disk device, which could lead to issues booting after patching of updating due to needed missing kernel modules for EVMS within initrd).
Still, even with it being possible and supported to do so, if you can house the OS bits and data (be it on NSS and other filesystems) on different disk devices.. that would always be what I'd opt for. It makes certain maintenance/recovery and update tasks easier/more flexible/reliable as OS and data partitions are not within one and the same "container".
Cheers,
Willem

NSS Volume missing disk space

Hi
I have a NW6.5 SP 8 server with Raid 5. One of the NSS volumes has a capacity of 67GB. There are only two directories on the volume, one 6GB and the other 14GB for a total of 20GB yet it shows only 3.5GB free. NSSMU, windows explorer and Treesize Pro all confirm these numbers. Where has the remaining 47GB gone? Any help finding it would be appreciated.

Hi,
rjfraser wrote:
>
> Hi
> I have a NW6.5 SP 8 server with Raid 5. One of the NSS volumes has a
> capacity of 67GB. There are only two directories on the volume, one 6GB
> and the other 14GB for a total of 20GB yet it shows only 3.5GB free.
> NSSMU, windows explorer and Treesize Pro all confirm these numbers.
> Where has the remaining 47GB gone? Any help finding it would be
> appreciated.
Probably some sparse or currently open and written to file. When you
produce a new file, keep it open, and continously write data to it, it's
size in Explorer will stick at 0bytes until it gets closed for the first
time, so explorer and treesize who simply add up the file size of all
files won't see it, but the free space on the drive will drop
nevertheless.
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

Last modified on NSS volumes?

I can get a list of files and their ***last accessed*** dates all day long. However, that time stamp got over-written by the backup software, so that if the file was accessed today, the backup software backed it up and re-stamped the access time to 12 midnight.
Is there a way to pull a list of last >>>modified<<< off of a NSS volume? The Netware TBX dir/ls command comes to mind, but the documentation isn't clear on this one (assume that the time/date stamp is last accessed or created?).
What about a BASH shell command?
Thanks!
Tim Wohlford

DSRAZOR for eDirectory can give you reports of files with any of the
following fields - last modified date, creation date, last accessed date,
last archived date, owner, size, and file attributes (inhibit delete, purge
immediate, etc). The NSS volumes can be on NetWare or Linux. The results
can be sent out to a CSV file or a TXT file.
We can customize the applet to fit your search criteria (if any) and which
information you want displayed in the report. For example, we could set it
up to show all files or only files that meet certain criteria and send the
results out to a CSV file that includes their last modified date, owner, and
size. If this is a report you will need to run regularly, the applet can be
saved as an EXE file to be automated with a task scheduler.
You can find more information about DSRAZOR for eDirectory here:
http://www.visualclick.com/?source=NVsupOESnw
"twohlford" <[email protected]> wrote in message
news:[email protected]..
>
> I can get a list of files and their ***last accessed*** dates all day
> long. However, that time stamp got over-written by the backup software,
> so that if the file was accessed today, the backup software backed it up
> and re-stamped the access time to 12 midnight.
>
> Is there a way to pull a list of last >>>modified<<< off of a NSS
> volume? The Netware TBX dir/ls command comes to mind, but the
> documentation isn't clear on this one (assume that the time/date stamp
> is last accessed or created?).
>
> What about a BASH shell command?
>
> Thanks!
>
> Tim Wohlford
>
>
> --
> Tim Wohlford, CNE
> ------------------------------------------------------------------------
> twohlford's Profile: http://forums.novell.com/member.php?userid=5748
> View this thread: http://forums.novell.com/showthread.php?t=456155
>

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

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

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

SBS and NSS Volumes

Similar Messages

Maybe you are looking for