Direct answer: A folder copy is not a complete backup. You need recoverable databases, configuration files, client assets and a record of which versions belong together.
Use four backup layers
| Layer | What to save | When |
|---|---|---|
| Original archive | Untouched package and source notes | Before extraction |
| VM snapshot | OS, runtimes, SQL installation and tools | At clean milestones |
| SQL backups | Full backup of every package database | Before scripts or editors |
| Config/client copy | Exact working files and hashes | Before each release or network change |
Name backups so they remain useful
Include package, component, state and sequence in the filename—for example, lab-auth-clean-01.bak or client-before-launcher-test.zip. Avoid calling every backup “final.” Keep a small text changelog beside them.
Test recovery, not just creation
Restore a database backup to a temporary name and verify that SQL Server can read it. Clone the VM snapshot and start it on an isolated network. A backup that has never been restored is only a hope.
Protect credentials
Configuration archives may contain database passwords and private addresses. Do not publish them with screenshots or share them in public download packs. Rotate credentials after accidental disclosure.
Recovery drills for real confidence
Restore to a different name
Testing a backup by overwriting the working database defeats the purpose. Restore to a temporary database name, verify its objects and then remove it. This confirms the backup is readable without risking the live lab.
Export configuration evidence
Keep screenshots or notes of SQL instance settings, authentication mode, service accounts, ODBC DSNs and firewall rules. Those settings are not all contained in the server folder and are easily forgotten during a rebuild.
Use off-VM copies
A snapshot stored only on the same failing disk is not enough. Keep at least one copy of databases and clean packages outside the VM. For important work, use a second physical device or reputable backup destination.
Practice the return to baseline
After testing an editor, deliberately restore the clean database and file copy. A five-minute recovery drill proves that experimentation is safe and exposes missing steps while the system is still healthy.
Package-specific values vary. Verify names, ports, database schemas and permissions against the files you are legally authorized to use. ZHowTo does not provide proprietary server files, anti-cheat bypasses or instructions for unauthorized access. Corrections: bugridez@gmail.com.