|
Component |
System environment |
|---|---|
|
Version |
Cross-version |
|
Created on |
|
|
Last modified on |
No Workflow Applied |
|
Review status |
No Workflow Applied |
|
KB article number |
406749378 |
Summary
You regularly update your server infrastructure, e.g. due to operating system updates or changes to the hardware or resource allocation.
For example, if you need to maintain your server landscape with d.velop documents and/or edoc platform, you may need to temporarily shut down and/or restart all servers.
With a complex server infrastructure, you must ensure the sequence for shutting down and restarting.
Important requirements
You need administrative permissions to shut down or restart the servers. We also recommend administrative permissions to check the Windows services afterwards.
xSuite server in server infrastructure
If you have an xSuite server in your server infrastructure, check carefully whether this server actually needs to be shut down and/or restarted.
The license of the xSuite application may become invalid, so you may often experience system downtime.
Solution
To avoid inconsistencies and problems when restarting the server infrastructure, we recommend the following sequence.
If you do not use individual servers, move on to the next server.
Sequence when shutting down the server
-
Server with edoc platform (Linux VM)
-
Server with the d.3 services (e.g. d.ecs rendition service, d.cold or d.capture batch, etc.)
-
Server with the d.3 applications (basic server with d.velop documents server processes)
-
Database server
Sequence when booting the server
Restart the servers in reverse order.
Make sure that the Windows services that start automatically are also restarted when the server is booted.
-
Database server
-
Server with the d.3 applications
-
Server with the d.3 services
-
Server with edoc platform