My tried-and-tested method has saved my (company’s clients) ass a few times.
Every Mysql/MariaDB server has at least one replication target. This replicant is not used for access by the infra, and can be paused, restarted, etc with no issue and is configured with this in mind.
We run a mysqldump on the replicant. Depending on the resiliency required, we store the dump on the replicant and/or a third location.
The tools differ, but the practice applies to pretty much every database system and the database has the benefit of not being interrupted during the backup (replication is paused during the backup, and resumed after completion). This also has the benefit of already having replication configured, and adding a secondary redundant instance you can swap out for the master (or using the backup replicant in a pinch) means disaster recovery is much faster.
Also, I dislike many things about Azure’s offerings, but their Flexible Database for MySQL does the above for you as one nicely packaged solution for a reasonable-but-not-cheap price.
The effect you are describing is “viral load”; the degree to which a virus is present in the body. This is an indicator of how infectious you are. It is especially important for people with HIV to see if they are “safe” or need their medication adjusted.
However, an at-home test will not be a good indicator of this. These have too many variables such as the site that was swabbed, time delays from the various biological functions, how well you used the kit and even variability in the kit itself.
To properly test for viral load, a blood test should be used. I worked with a company that tested for viral load via expelled breath, and while this was a good indicator of infectiousness y/n, and was faster than a PCR, it was not more accurate.