05.02.2013 Views

opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2 - opsi Download - uib

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>opsi</strong> <strong>manual</strong> <strong>opsi</strong> <strong>version</strong> <strong>4.0.2</strong><br />

Figure 82: Scheme <strong>opsi</strong> multi depot environment<br />

152 / 193<br />

As the figure points out there is only one server which have data storage for the configuration data - the data backend.<br />

This is the <strong>opsi</strong> config server. The <strong>opsi</strong> depot server has no own data storage but a redirected backend. This means<br />

that if you ask a depot server for any configuration data, this question will be redirected to the config server. And<br />

this leads to the consequence that every check which runs against the <strong>opsi</strong> data backend will at least run on the config<br />

server. So you should address checks that run against the backend always to the config server. Even in the situation<br />

if you are collecting information about clients which are assigned to a depot which is different from the config server<br />

and the check is logically part of the check of this depot server.<br />

If you running direct checks you normally also address the config server. You may address the depot server if the<br />

clients can’t be reached by the <strong>opsi</strong> config server via port 4441. In this case it is a good idea to address the depot<br />

server.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!