If I understand what you are saying, I need to have a NetWorker Server installed on Windows, with a repository cdpb in order to update the repository on another Windows box? I guess the same is true in reverse, I would need a Linux NetWorker server in order to update the repository on a Linux server?
So, in a mixed environment (Linux/Windows) I need 2 NetWorker Servers?
NW adds the software to the repository via a 'save' process. This implies that the Windows software packages must be transfered from a Windows client. The repository can be on any host.
Came across a similar error, solution was to provide complete set of binaries instead of just client binaries from the setup extract. Though the error was deceptive.
davidnw137
5 Posts
0
October 15th, 2014 10:00
Thanks for the quick reply.
If I understand what you are saying, I need to have a NetWorker Server installed on Windows, with a repository cdpb in order to update the repository on another Windows box? I guess the same is true in reverse, I would need a Linux NetWorker server in order to update the repository on a Linux server?
So, in a mixed environment (Linux/Windows) I need 2 NetWorker Servers?
Thanks,
David
bingo.1
2.4K Posts
0
October 15th, 2014 10:00
The old story...
NW adds the software to the repository via a 'save' process. This implies that the Windows software packages must be transfered from a Windows client. The repository can be on any host.
bingo.1
2.4K Posts
0
October 15th, 2014 14:00
No - of course one repository can keep all software packages. No matter of which OS type.
But to add SW to the repository, it must be added from a client of the same OS type family.
SurajPujari
155 Posts
0
May 14th, 2018 05:00
Came across a similar error, solution was to provide complete set of binaries instead of just client binaries from the setup extract. Though the error was deceptive.