Not exactly, it is like mounting a physical drive volume as a directory of
another drive:
C:\>mountvol
Creates, deletes, or lists a volume mount point.
MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
path Specifies the existing NTFS directory where the mount
point will reside.
VolumeName Specifies the volume name that is the target of the mount
point.
/D Removes the volume mount point from the specified directory.
/L Lists the mounted volume name for the specified directory.
Possible values for VolumeName along with current mount points are:
\\?\Volume{5e821af0-0d2e-11d6-b759-806d6172696f}\
C:\
\\?\Volume{45e46af0-0d32-11d6-9c55-806d6172696f}\
*** NO MOUNT POINTS ***
\\?\Volume{45e46af1-0d32-11d6-9c55-444553544200}\
D:\LinuxXfr\
\\?\Volume{5e821af1-0d2e-11d6-b759-806d6172696f}\
D:\
\\?\Volume{ebee28d0-ddbb-11d5-984d-444553544200}\
E:\
\\?\Volume{aa12fac1-fd18-11d4-8055-00000ed4bacf}\
F:\
\\?\Volume{91a1e0c1-fd16-11d4-af0f-806d6172696f}\
A:\
C:\>
Pay attention to "D:\LinuxXfr\, it is another disk mounted under D:\
C:\>mountvol D:\LinuxXfr /L
\\?\Volume{45e46af1-0d32-11d6-9c55-444553544200}\
I did a backup of drive D: using Networker 7.0 and the directory is listed
but none of the subdirectories and files on the volume under the mountpoint.
The volume itself has not been backed up because it does not have a drive
letter.
Bye
Ernie
-----Original Message-----
From: Reed, Ted G II [ITS] [mailto:ted.reed AT MAIL.SPRINT DOT COM]
Sent: Friday, May 09, 2003 9:27 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Billions upon billions of bytes ignored by
networker
Also known as "mapping a network drive" in WinSpeak.
-----Original Message-----
From: Narkinsky, Brian [mailto:Brian.Narkinsky AT DEP.STATE.FL DOT US]
Sent: Friday, May 09, 2003 1:06 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Billions upon billions of bytes ignored by
networker
Basically the same thing. It allows you mount a physical drive volume as a
directory of another drive.
-----Original Message-----
From: Minson, John Spawar [mailto:john.minson AT NAVY DOT MIL]
Sent: Fri 5/9/2003 1:32 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Cc:
Subject: Re: [Networker] Billions upon billions of bytes ignored by
networker
I know what a 'mount point' is in unix but I don't know what it is
in W2K/WNIN NT etc
-----Original Message-----
From: Itzik Meirson [mailto:imeirson AT MBI.CO DOT IL]
Sent: Friday, May 09, 2003 1:10 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Billions upon billions of bytes ignored by
networker
Could it be that the skipped directory is set up as a mount-point in
your Windows client configuration?
Itzik
-----Original Message-----
From: Jon Minson [mailto:john.minson AT NAVY DOT MIL]
Sent: Friday, 09 May, 2003 15:14
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Billions upon billions of bytes ignored by
networker
It would would be a nice feature for Networker to give some
warning/error/explanation when it decides to ignore W2K directories
containing billions of bytes of data . Yes thats whats happening
here
.
Its happened on 2 different W2K servers of dissimilar
configurations.
The setup is
1) W2K server running Networker 6.1.2 client (or greater) 2)Solaris
2.6
running Networker 6.1.2 or 6.1.3 server Heres the ugliness
In one case the drive on the W2K box was 'E:\" in another case
"F:\".
In
the client setup I said 'ALL' for the savesets. After the backup
runs
you see that a particular directory(lets say XYZ) containing in one
case
70 GB data does not get backed up. Review of both server and client
logs
shows NO ERRORS/NO WARNINGS . This is not good.Further inspection of
the
backup results shows that some of the data on "F:\" was dumped ,
only
XYZ was ignored. I then go on to discover that by listing the
directories explicitly (F:\A F:\XYZ F:\FUBAR) every thing gets
dumped
.
This is not a good solution for obvious reasons .
I have been struggling with this issue since last October. Legato
'technical' support must not think its much of an issue since I'm
the
only one reporting it.(We go through a 3rd party for support).
Is it a Networker BUG? W2K BUG? Networker Config Issue? W2K Security
Issue? W2K Config Issue ? I don't care . I have supplied every log
available form both server and client,every configuration detail
from
both server and client. Silence . All manner of back up tests run .
Silence
If you have a configuration similar to ours you might want to double
check your back up results.
Heres some real data.
# savegrp -n -c xxxx -G TEST
xxxx:C:\ 8004 records 1585 KB header 872 MB data
xxxx:C:\ 874 MB estimated
xxxx:E:\ 96 records 18 KB header 11 MB data
xxxx:E:\ 11 MB estimated
xxxx:F:\ 240 records 51 KB header 424 MB data
xxxx:F:\ 424 MB estimated
xxxx:SYSTEM STATE:\ 4 records 1 KB header 0 KB data
xxxx:SYSTEM STATE:\ 1 KB estimated
xxxx:SYSTEM DB:\ 4 records 1 KB header 0 KB data
xxxx:SYSTEM DB:\ 1 KB estimated
xxxx:SYSTEM FILES:\ 2 records 1 KB header 0 KB data
xxxx:SYSTEM FILES:\ 1 KB estimated
SSSSS:index:8cfbc825-00000004-3d09d4b4-3d09d4b3-04670000-ac112846
352
records 72 KB header 26 MB data
SSSSS:index:8cfbc825-00000004-3d09d4b4-3d09d4b3-04670000-ac112846
26
MB estimated
Notice the estimate for F:\
Now by listing F:\XYZ we see
# savegrp -n -c xxxx -G TEST
xxxx:F:\XYZ 17689 records 4094 KB header 71 GB data
xxxx:F:\XYZ 71 GB estimated
SSSSS:index:8cfbc825-00000004-3d09d4b4-3d09d4b3-04670000-ac112846
352
records 72 KB header 26 MB data
SSSSS:index:8cfbc825-00000004-3d09d4b4-3d09d4b3-04670000-ac112846
26
MB estimated #
Slight difference between 424 MB and 71 GB
--
Note: To sign off this list, send a "signoff networker" command via
email to listserv AT listmail.temple DOT edu or visit the list's Web
site
at
http://listmail.temple.edu/archives/networker.html where you can
also
view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
****************************************************************************
*
*********************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system
manager or the
sender immediately and do not disclose the contents to any one or
make copies.
MBI - System Team
****************************************************************************
*
*********************
--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
