In regard to: Re: [Networker] Windows DFS Junction warning messages,...:
Why ?
For the same reason you have to explicitly list any NFS mounted
filesystem on a Unix/Linux client if you want NW to back them up, it's
not considered a 'local' filesystem by NW, so it does not see it as
something that needs to be backed up unless YOU put it in the list of
save-sets you want backed up...
At the risk of sounding like a two year old with a continuous stream of
"why?", *why* isn't it considered a local volume?
I fully understand NFS between two systems; NetWorker's "All" doesn't
back up the volume on the client system because it's not a local volume.
The client is getting that volume from some other system. You can force
NetWorker to back it up on the client if you specify it explicitly.
In our case, though, these DFS Junctions are completely local to the box.
It's not the case that "wserv1.ndsu.edu" is mounting K: from some other
system -- it's a local volume.
We backup NFS mounted filesystems on Unix/Linux this way...
I totally understand, but in that case it's clear that the actual storage
is coming from some other system.
In our case, there's no "other system". It's a local volume that's
mounted under K:. I'm just not getting why that's any different than
a local volume on a Linux system mounted under e.g. /home or /var.
I do appreciate all the responses so far, but I'm afraid at this point I
still don't understand why this is different than any locally mounted
filesystem on a Linux, UNIX, or even NetWare system.
Tim
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Tim Mooney
Sent: Tuesday, April 03, 2012 2:15 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Windows DFS Junction warning messages
In regard to: Re: [Networker] Windows DFS Junction warning messages,...:
You have to open up the client resource in the NetWorker administrator
GUI and in the savesets section, list out all the disks and DFS mount
points you want to back up on that client.
That's the part I don't get: *why* do I have to do that?
On a UNIX or Linux client, the "All" saveset backs up all mounted, local
filesystems that are listed in the mnttab or it's platform-specific
equivalent. If /var and /home are separate filesystems, mounted in the
"var" and "home" directories (mountpoints) under /, I don't need to do
anything special to get them to be backed up. "All" takes care of it.
So why doesn't "All" do the same thing on Windows?
Tim
All-
We've been backing up Windows systems to our (previous) UNIX and now
Linux NetWorker servers for 15+ years. Our Windows admins are
preparing to roll out Windows-based file services to replace our
NetWare file servers, and we've encountered a warning that I don't
understand.
The warning is this:
--- Successful Save Sets ---
* wserv.ndsu.edu:All savefs wserv.ndsu.edu: succeeded.
* wserv.ndsu.edu:K:\ 69435:save: DFS Junction/Mountpoint detected:
files/directories under `K:\DFSRoots\home\' will not be backed up. To
back up a DFS Junction/Mountpoint, specify the DFS Junction/Mountpoint
as the saveset value.
* wserv.ndsu.edu:K:\ 69435:save: DFS Junction/Mountpoint detected:
files/directories under `K:\DFSRoots\shared\' will not be backed up. To
back up a DFS Junction/Mountpoint, specify the DFS Junction/Mountpoint
as the saveset value.
wserv.ndsu.edu: K:\ level=full, 911 KB 00:02:03 14 files
One of our Windows admins did some searching in Powerlink and turned
up esg91909, "Error: 'Mountpoint detected' when performing backups",
which basically says that NetWorker doesn't backup up mounted
filesystems, and goes on to later state that "mountpoints are not
crossed" on any platform.
That's complete bunk; NetWorker will certainly cross mountpoints on
UNIX & Linux systems, as long as we're talking about *local* volumes.
I'm not a Windows guy, so I have to believe there's something going
on here that I don't understand. Why is it warning me about DFS
mountpoints on the Windows system? Is it that
- DFS mountpoints work more like a symlink, in that the data actually
resides elsewhere on the system but it's presented to the user or
client system as if it was under K:?
or
- DFS mountpoints are considered non-local volumes, akin to an NFS
mount on UNIX/Linux?
Anyone care to clarify what's going on here?
Thanks,
Tim
--
Tim Mooney
Tim.Mooney AT ndsu DOT edu
Enterprise Computing & Infrastructure 701-231-1076
(Voice)
Room 242-J6, IACC Building 701-231-8541
(Fax)
North Dakota State University, Fargo, ND 58105-5164
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with
this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
--
Tim Mooney Tim.Mooney AT ndsu DOT
edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
