Good! Glad to hear it. Just a word of caution ... account/site backups are only as good as when they were made. Example: so if the last SiteGround account backup was made a week ago and that's what is restored ... yes, the code gets reverted back (problem solved there), but so does the database on an account restore. Moodle sites that are used on a daily basis might now be missing student work. Besides that, there is the database files themselves ... RackSpace, as an example provider, warns that raw copy of files and raw restore of database files are a risk and that they cannot be held responsible when full-filling the customer request should the db files be corrupted. The same is probably true of every hosting provider.
Dodge a bullet? Lucky you! Uhhhh .... safer yet not to be in the line of fire! Strongly suggest setting up a daily sql dump of the database that reside on the server itself. SiteGrounds restore will include those .sql files. So it's kinda like insurance if the raw copy of files gets putzzed at least OP has one .sql file to restore. That suggestion should attract attention of some community members who would suggest taking that a step further.
Bottom line is ... one can never have enough backups ... account, site, and the parts an pieces that make a moodle run ... code + sql dump + moodledata/filedir (last one a minimum).
In many years experience at hosting remotely and running Linux/open sourced apps like a Moodle, never regretted taking the extra time to backup and archive remotely those backups.
Am sure you will have a better/restful weekend!
Good thinking on your part!
'spirit of sharing', Ken