In regard to: RE: [Networker] strange Windows volume name when using All...: One thing you could do is change the save set definition to ALL-NTFS - assuming that all your file systems are NTFS .... p
In regard to: Re: [Networker] Library no longer autochanging tapes, Werth,...: Batch labeling works just fine. NW does send the alert "Waiting for a writable tape for pool xxx" and there are perfectl
Author: "Werth, Dave" <dave.werth AT GARMIN DOT COM>
Date: Tue, 23 Jul 2013 23:01:12 +0000
You pretty much saw the whole conversation in that one post. That's a good suggestion to try the mminfo commands. I'll try them next time this happens. From the NMC everything looks fine. Dave Werth
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Tue, 23 Jul 2013 21:11:37 -0700
Do not forget that if you use the 'location' field adn use it for naything else but the jukebox name, NW will also not be able to use it - even if it is inside the jukebox. NW will also not be able t
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Wed, 24 Jul 2013 09:28:09 -0400
I'm having an odd problem. I have a client that I recently upgraded to NW client 8.0.2. Now, it seems that every Windows client I upgrade to NW 8.x needs to have save -a "ignore-all-missing-system-fi
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Wed, 24 Jul 2013 09:48:23 -0400
NW 8.x with It's type: savepnpc; precmd: "C:\\PHA_Sc~1\\SuspendSourceOne.CMD"; pstcmd: "C:\\PHA_Sc~1\\ResumeSourceOne.CMD"; abort precmd with group: No; requires production command points have Do I
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Wed, 24 Jul 2013 07:10:44 -0700
The most obvious way would be to use 2 client resources like ... the file backup client ... Save Set: All-NTFS Backup Command: savepnpc the VSS backup client ... Save Set: VSS.... Backup Command: sav
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Wed, 24 Jul 2013 10:58:23 -0400
I'm not certain that would help, although it is quite ingenious. I need to be able to do a BMR recovery of this server, and - since it's Win 2008 R2 - that means I need to do a DISASTER_RECOVERY: sa
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Wed, 24 Jul 2013 11:22:19 -0400
(Automatic Apparently not. Here is a DISASTER_RECOVERY: only job I happened to run on that server a few weeks ago: * SERVER01:DISASTER_RECOVERY:\ 77775:savepnpc: Processing completed for disaster re
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Wed, 24 Jul 2013 11:34:10 -0400
AH HA! In this one particular case, the failure is on a copy of the file pds.exe: * DISASTER_RECOVERY:\ System Writer - Get file attributes returned error 3 for VSS file \\?\GLOBALROOT\Device\Harddis
Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>
Date: Wed, 24 Jul 2013 13:50:44 -0400
Michael, It appears that savepnpc also will parse the -a argument... so, I'd suggest you try: savepnpc -a "ignore-all-missing-system-files=yes" as your backup command. EMC should be able to tell you
Author: "Clark, Patricia A." <clarkpa AT ORNL DOT GOV>
Date: Wed, 24 Jul 2013 18:24:16 -0400
I have several clients slated for migration to a new networker server. The first client is a Windows 2008R2 server that was recently upgraded to v8.0. It has been managed by a Windows networker serve
All We're preparing to do initial setup and integration of our brand new Data Domain 860 with NetWorker and I'm looking for advice from experienced Data Domain users on whether what we're wanting is
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Wed, 24 Jul 2013 20:52:46 -0700
" I added the client with its clientid to the server." I doubt that using the same clientID is really necessary as both NW servers have independent databases. "Nada." Nada what? - does the NW service
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Thu, 25 Jul 2013 00:28:04 -0700
I am still convinced that my 2-client resource solution will work. However, there are some restrictions to follow: 1. Of course you will need the save set "DISASTER RECOVERY:\". I did not mention thi
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Thu, 25 Jul 2013 08:55:08 -0400
As I pointed out, the DISASTER_RECOVERY: saveset includes all drives for this server. So you get duplicate backups, if you use the 2 client definitions you suggest. (and probably errors in one of th
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Thu, 25 Jul 2013 07:05:53 -0700
"As I pointed out, the DISASTER_RECOVERY: saveset includes all drives for this server. So you get duplicate backups, if you use the 2 client definitions you suggest." That was correct but it depends
Author: "Clark, Patricia A." <clarkpa AT ORNL DOT GOV>
Date: Thu, 25 Jul 2013 10:06:58 -0400
Thank you bingo. Your reply gave me the starting point to resolve the issue. First, the client was running without issue and the logs had nothing in them regarding connections being made or not. Usin
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Thu, 25 Jul 2013 07:12:56 -0700
Tim, we actually also used our DDs with 2 separate 10GB NICs to the storage nodes. However, we found that sooner or later this might obviously cause problems and we switched to the solely 10GB networ