CHR Snapshots and Payment Database Rollback

This guide covers CHR snapshots. Start with the checks below. Then compare your result with the example before changing a live service. A virtual-machine snapshot and a billing backup are different recovery mechanisms. Rolling back an entire machine can reintroduce old application state if the billing database is stored there.

CHR snapshots: practical checks

1. Identify exactly which disks and databases a snapshot includes.
2. Record payment activity occurring after the recovery point.
3. Reconcile restored records before accepting new renewals.

CHR snapshots: a working example

If a snapshot predates three confirmed purchases, restoring it may hide their application records while the merchant still has the payments. Review those transactions rather than collecting again.

First, write down the starting state and the expected result. Then make one controlled change. Next, compare the result with the example above. Finally, record what changed and who should follow up. Keep private account details out of shared notes.

Where LinkDesk fits

LinkDesk is a separate billing application, not a CHR licence or virtual hosting service. A proposed virtual deployment needs a tested application-to-router path, suitable infrastructure and a separate decision about the RouterOS licence.

For the tool or product details behind this guide, see LinkDesk features and current limits. The checklist and example above are WayaDesk’s operating guidance.