Informational and non-binding guidance (not part of the Software License) October 11, 2026
This document gives practical examples only. It is not incorporated into the CH-J Server Manager Proprietary Software License, does not impose separate contractual obligations and does not promise error-free operation or recovery. Operators should adapt safeguards to the affected systems, applicable laws, their permissions and the foreseeable risk. The relevant provisions are Sections 3.5 and 7.2 of the applicable CH-J Server Manager Proprietary Software License. Reading or following these examples is not a separate contractual requirement.
1. Protect data on connected systems
- Identify important server files, databases, application state, access-control data, and system configurations that could be affected by an operation.
- Keep backup copies sufficiently independent from the live system so that an erroneous command, ransomware, hardware failure or accidental deletion is less likely to destroy the originals and the backups together. Options include separate storage and access controls, immutable or offline copies when appropriate.
- Make sure the backup frequency and retention are appropriate for acceptable recovery-point and recovery-time objectives.
- Periodically confirm that backups exist, are readable and can be restored. A copy that cannot be restored provides little protection.
- RAID, mirrored disks, snapshots or high availability may be useful, but do not always replace independent, recoverable backups.
- When managing a client's or employer's systems, coordinate with the authorised backup owner. Do not copy restricted customer data to personal storage or access data without permission.
2. Test before risky operations
The Software License (Section 3.5) explains the release-stage status and warnings. This guidance adds no separate restriction or legal condition.
- On a staging or non-production server when feasible, exercise only the application functions you plan to rely on, especially file writes, bulk operations, SSH commands, permission changes and automated jobs.
- Test with non-sensitive or disposable data, confirm the selected target systems and identities and consider a dry run where available.
- Test relevant functions again after material application updates, changed server permissions, configuration changes or changes to automation.
- If no suitable staging environment exists, consider a reduced-scope operation, additional confirmation, backup checks and a clear rollback plan.
- Avoid unnecessary privileged sessions; limit credentials to the actions actually needed.
3. Hashing and integrity checks
- Local hashes and checksum comparisons can help detect accidental or deliberate changes, but the result is meaningful only when compared with an expected value obtained from a trustworthy source.
- For security-sensitive integrity checks, prefer modern cryptographic hash algorithms such as SHA-256 or SHA-512. MD5, SHA-1 and non-cryptographic checksums are not appropriate proofs of security against deliberate modification.
- The local hash tool does not itself back up data or prove that a remote server is uncompromised.
4. Higher-risk environments
CH-J Server Manager is for general system administration, not for performing a safety-critical protection, control or emergency function. A connection to an organisation that operates critical systems does not by itself make ordinary IT administration a safety-critical use. Determine whether the specific system or process you manage can directly impact life or health, and consult the organisation's required procedures and qualified safety personnel.
5. After an incident
Preserve relevant logs without exposing credentials, stop destructive tasks if safe, notify the authorised operator, and follow the system owner's incident-response and restore process. Do not assume that an automated retry is safe.
This guidance is educational, optional and non-binding. It does not change the Software License, impose additional legal duties or limit statutory rights.