• Making changes to service configurations.
• Service optimization.
• Log file analysis and check.
• Performing speed, load, and other tests.
• Analysis of load graphs.
• Data recovery from backup.
• Finding solutions for technical, OS-specific issues.
• Changing the operating system and kernel settings.
• Making suggestions for adding, updating, or replacing hardware or software.
• Responding to information requests about the server or its documentation.
• Relevant consultation.
• Fixing all errors directly caused by Lumav’s actions within its responsibility area.

The audit is a methodological, detailed server review process based on specific points, detailed in the company’s internal documentation. In brief, it includes:

• In-depth analysis of information read by Lumav’s monitoring system (see Automated Tasks).
• Analysis of server load graphs.
• Check of hardware age, BIOS, firmware versions, disk checks.
• Verification of software updates on the server and mapping possible solutions.
• Check of server standardization.
• Review of the server’s current state (processes, open ports, network quality, disk speed).
• Check of correct operation of automatic scripts (cron).
• Analysis of login history and service usage frequency.
• Check of logging capabilities and more detailed log file analysis.
• Check of data on file systems (for rootkits, worms, viruses).
• Firewall audit.
• Network security scanning.
• Security check of service and application configurations (postfix, apache, php, dns).
• Backup check.
• If necessary, physical server check (secure location, security, access control, etc.).
• If the server is managed by Lumav – validation, restructuring, and updating of server documentation.

Additional work is performed by prior agreement, at an hourly rate or agreed project fee. Additional work includes tasks not listed in the previous points or outside Lumav’s contractual responsibilities. Examples of additional work:

• Work outside working hours or on an urgent basis (faster than the corresponding service package allows).
• Installation or configuration of services or applications not specified in the contract.
• Server installation or reinstallation.
• Major updates (e.g., distribution version major update).
• Data migration from one service provider to another or from one service/solution to another.
• Backup-related work not concerning specific one-time restoration work (e.g., searching for vaguely specified data in the archive, testing different versions).
• Training and consultation not related to specific ordered services.
• Configuration and management of custom solutions or non-standard software.
• Development, programming, and script writing work.
• Any significant modification work.
• Any work outside the principle of smooth operation.

Regular work may become additional work under the following circumstances at Lumav’s request:

• Administrator access rights have been confirmed by the Client for third parties, and there is reason to believe that the need for work was caused by their actions or negligence.
• The need for work arose from the Client’s actions in a service layer that should be under Lumav’s responsibility. This does not apply if the action was previously coordinated with Lumav.
• The need for work arose from the Client’s inactivity when Lumav had previously notified and justified the need for the activity.