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.

Similar Messages

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.

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/

Per-user web directory on nss volume

Is possible to use directories in nss volume as per-user web directory for apache virtual hosts ?
How I set permission for it ?
Vogl Lubomir

vogl,
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://support.novell.com/forums/

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

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
>--------------------

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?

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/

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

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

Force immediate compression in NSS volume

Hi all,
We are migration our NSS file system from a server with OES2 to a new server with OES11. The size of the source disk is the same as the size of the target disk.
We have compression enable on booth servers.
The problem is that when we made the copy with "migfiles" command, the destination files were uncompressed and the copy failed because the target disk became full.
Are there any way to force an immediate compression on the target NSS volume (OES11sp2 with latest patch).
Thanks in advance!
Cristian

Hi.
Am 27.04.2015 um 16:36 schrieb crisgalante:
> The problem is that when we made the copy with "migfiles" command, the
> destination files were uncompressed
That shouldn't happen, and needs to be checked into closer. As you say
you're calling migfiles directly, what's the command line? Also, what
patch lever do both servers have?
> Are there any way to force an immediate compression on the target NSS
> volume (OES11sp2 with latest patch).
No, there's not, and it's not the proper approach.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

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

Strange directory behaviour on NSS volume OES11 SP1

Similar Messages

Maybe you are looking for