β04-22-2013 02:30 PM
Hello,
I was looking at the output of the bpplclients command and I'm seeing some odd stuff. My question is how much does the information in the OS and Hardware colums matter? For example I see Items in the OS such as winLonghorn64Guest and windows7Server64Guest. No workstations are being backed up. Only Solaris 10, Windows 2008 R2, RHEL 5 and SELS 11 SP2 are backed up. I have changed some of the host info via the GUI. Other items don't match what is in the GUI.
My main question is do I need to fix this stuff, or is this not so important? How can this affect my backups?
Servers OS being used.
Solaris 10 (1 master server, 1 media server)
Windows 2008R2 ( 1 meda server, all other servers are VMs -ESXi)
SUSIE 11 SP2 (all servers are VMs -ESXi)
RHEL 5 (all servers are VMs -ESXi)
I have removed the hostnames because I'm not allowed to post them.
< sudo /usr/openv/netbackup/bin/admincmd/bpplclients
Hardware OS Client
--------------- ----------------------- --------------
Solaris Solaris10
Solaris Solaris10
Solaris Solaris10
Solaris Solaris10
Solaris Solaris10
Solaris Solaris10
Solaris Solaris10
Windows-x64 Windows2008
Windows-x64 Windows2008
Solaris Solaris10
Solaris Solaris10
Linux SuSE2.6.16
vmx-07 winLonghorn64Guest
vmx-07 winLonghorn64Guest
Windows-x64 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
Solaris Solaris10
Linux SuSE2.6.16
Linux SuSE2.6.16
Solaris Solaris10
vmx-07 other26xLinux64Guest
vmx-07 windows7Server64Guest
Windows-x64 WindowsVista
Windows-x64 WindowsVista
Windows-x64 Windows2008
vmx-07 windows7Server64Guest
Windows-x64 Windows2008
vmx-07 windows7Server64Guest
Windows-x86 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
vmx-07 windows7Server64Guest
vmx-07 windows7Server64Guest
vmx-07 winNetStandardGuest
vmx-07 windows7Server64Guest
vmx-07 windows7Server64Guest
vmx-07 windows7Server64Guest
vmx-07 windows7Server64Guest
Windows-x64 Windows2008
Windows-x64 Windows2008
Windows-x64 Windows2008
vmx-07 windows7Server64Guest
vmx-07 windows7Server64Guest
vmx-07 windows7Server64Guest
Solaris Solaris10
Solaris Solaris10
Solaris Solaris10
Linux SuSE2.6.16
Solaris Solaris10
Solaris Solaris10
Solaris Solaris10
Solaris Solaris10
NDMP NDMP
Linux SuSE2.6.16
Solaris SunOS
Solaris Solaris10
Solved! Go to Solution.
β05-02-2013 01:47 PM
I still haven't thought of anything else.
A while back I configured a test server from the command line, I couldn't remember the exact syntax for 'linux' when configuring a client so just stuck it as solaris, it worked.
Hence my suggestion that I don't think it matters.
Howabout you correct a couple of the servers that fail, do they then work ? ... I certainly don;t mind being proved wrong if it gets the issue fixed.
What is the error that these clients fail with ?
I just noticed you said these clients 'fail often' - that would suggest they sometimes work. I would image that if this slight config issue was having an effect, they would fail 100% of the time.
Martin
β04-22-2013 02:58 PM
I'm thinking that we only really use this info if doing a push install of the client software out to the server, but there could be a reason I haven't yet thought of ...
That said ....
Do the backups work
Do restores work
If the answer is yes to both, then it would be reasonable to suggest that the important bits work, and if there is anything I haven't thought of, it is perhaps not too important.
If I think of anything, I'll report back ...
martin
β04-22-2013 07:00 PM
I would have to agree with mph999. In addtion vmx-07 is vmware.
Please see http://www.symantec.com/docs/HOWTO44451
http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=HOWTO70884
β04-22-2013 10:25 PM
OS does not matter in backup and restore. Its policy type and client name .
Hope it helps!
β04-23-2013 07:05 AM
mph999,
I was looking at this file because we just updated NetBackup from 7.1 to 7.5. Are backups work for the most part. Some of the Windows servers that fail offten, also have wrong info in the above command. For example list below and some of the servers that act up and what they are.
vmx-07 windows7Server64Guest sqlserver
vmx-07 winLonghorn64Guest exchange server
I'm reading the links you posted. Thanks
β05-02-2013 08:49 AM
β05-02-2013 01:47 PM
I still haven't thought of anything else.
A while back I configured a test server from the command line, I couldn't remember the exact syntax for 'linux' when configuring a client so just stuck it as solaris, it worked.
Hence my suggestion that I don't think it matters.
Howabout you correct a couple of the servers that fail, do they then work ? ... I certainly don;t mind being proved wrong if it gets the issue fixed.
What is the error that these clients fail with ?
I just noticed you said these clients 'fail often' - that would suggest they sometimes work. I would image that if this slight config issue was having an effect, they would fail 100% of the time.
Martin