You are micromanaging your backups. NetBackup is supposed to remove the manual complexities.
You should not be labeling the tapes as the same names as previous tapes that are full.
Can't tell you why it's happening. Does it happen often or infrequently?
Can you raise the logging level of your nbsl log to 6 and when it core dumps, note the time of the core and gather the raw log file for nbsl for that timeframe.
Also collect the core and also run a pstack <core> and pfiles...
goace,
NetBackup allows the installation of NetBackup using the install_client command from a Master or Media server.
Also what sort of "repetitive" manual tasks are you referring to?
FileSaver, no worries. Just remember. If that media server is in use and you have other backups running. Its a good idea to change policies to use another storage unit (or deactive them) and to deactivate the media server:
vmoprcmd -deactive_host -h <device_host>
The outcome is, this configuration is not supported.
Clients must always be at the same or lower version that the media server. Media servers must be the same or lower versions than the Master.
You need the server patch as well as the CLT (client patch).
If you're updating the Master/Media - good idea to update the Java patch too.
so you need
NB_CLT_6.5.3 <-client
NB_6.5.3 <- Server
NB_JAV_6.5.3 <- Java
by small I mean 640x800, windows has the option to change to 800x600 but when I apply it it goes back to 640x800.
I've tried adding the following to the .vmx file and restarting the Virtual Machine but it made no difference:
svga.vramSize = 1920000
svga.maxWidth = 800
svga.maxHeight = 600
Hi, I've just installed Windows 2000 Server onto my VMWare Server and when Windows boots the window size is really small.
I've tried adjusting the resolution but it doesn't work.
I'm sure many of you may have come across this in the past.
Any ideas or pointers would be really appreciated.
Cheers
Al,
I've never come across this before. Did you upgrade the NB_JAVA to 6.5 too?
Do you use VxSS?
Have you tried setting the auth.conf back to what it was prior to the upgrade?
Hi I am trying to run two windows managers on SuSE ES 10 (x86_64). One on display :0 (which works fine) and one on display :1
When I try and run it on :1 I get the message "twm: another window manager is already running. On screen 0?"
Does anyone have any tips to get around this?
Thanks in...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.