| Title: | NetWorker |
| Notice: | kits - 12-14, problem reporting - 41.*, basics 1-100 |
| Moderator: | DECWET::RANDALL .com::lenox |
| Created: | Thu Oct 10 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 750 |
| Total number of notes: | 3361 |
Hi, A client has two AlphaServer 4100s with Windows NT 4.0 and Digital Clusters for Windows NT 1.1. DECNSR 4.3 server is on one of the Cluster member (serverA) and hosts a DLT drive. NSR client is on the other Cluster member (serverB). Both serverA and serverB host cluster disks. ServerA's local and cluster disks can be backed up ok using a scheduled backup job. The client wants to back up serverB using the NSR Server Admin scheduling features, but if a job is scheduled in this way only the LOCAL disks on serverB are backed up. He can only backup the cluster disks hosted by serverB if he runs the NSR client on serverB - a manual process. Is there a difference in the way the client and server identify "local" disks? Should he expect it to work to a "remote" cluster node? Do the cluster disks look like "network drives" to the DECNSR client, perhaps, but not to the server? Any feedback would be appreciated. [cross posted in decwet::winnt-clusters] Thanks & regards, Adrian Moore Sydney CSC Out of my depth and floating away... [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 723.1 | montlake.zso.dec.com::lenox | posted with NetNotes | Fri May 30 1997 09:11 | 10 | |
There shouldn't be a difference, but I don't think we tried this with 1.1. Are they using saveset All in both client definitions? You see the server talks to the client part even on the system the NetWorker server is on, so it should be behaving the same. The shared filesystems should not look any different to NetWorker. I'll check out if Mark or Carl has noted anything in the clusters conference before I say much more... | |||||