Define what must be recoverable
For an On-Premise deployment, retain the application database, required application data and configuration as a coordinated recovery set. This guide describes an administrator-run backup procedure; it does not claim a built-in one-click DeskGate backup feature.
Agree how much data loss is acceptable and how quickly service must return. Those requirements determine the backup schedule and whether the DBA needs differential or transaction-log backups in addition to full backups.
Inventory the recovery set
- Record the installed application and SQL versions, actual database, installation folder, static IP, web access mode and ports.
- Identify App_Data and other customer-maintained files required by the release.
- Keep the license and required configuration securely, including the Sql.udl connection configuration and relevant GoMyit server settings.
- Retain the matching approved application release and a recovery runbook.
- Keep any keys or certificates required by the chosen database encryption or backup method.
Take the database backup
Have the DBA create a full backup of the actual application database using SQL Server’s supported backup tooling. In an existing SSMS installation, select the database, Tasks → Back Up, verify Database and Full, then choose a controlled destination. Follow Microsoft’s full-backup instructions for your version and backup policy.
For an additional maintenance backup, ask the DBA whether copy-only is appropriate to avoid changing the existing differential backup strategy. Copying live MDF/LDF files is not a substitute for a supported database backup.
Coordinate application files and protect the result
Use an agreed maintenance window or a consistency method validated by the administrator to align database and application-file recovery points. Do not assume files copied at unrelated times form a coherent recovery set.
InstallationReport files can include the actual SQL password. Treat them and connection files as secrets. Store backup copies with restricted access and retention outside the installation directory; protect against loss of the original host.
Prove recovery
Record backup time, database, application version, destination, result and owner. A successful backup job is not the end of verification: carry out an isolated restore test, confirm application startup and inspect representative data. See DeskGate Restore Guide.
For recording-age settings and storage planning, see Data Retention and Disk Management.