For all 1 of my readers holding your breath wondering how the backup plan came out (or since this blog is late, I guess for those of you 1 on respirators) , it turned out we did have a backup plan in place!
I can’t believe you doubted me.
A server timer job is set to run a STSADM batch file each day in the evening to do a full farm, catastrophic backup, with incremental SQL Server content backups periodically through the day. Thanks, Todd Klindt for verifying that a full recovery was possible from these backups.
True confession, however: recovery from the backup has not been tried on my watch. Like in the real world. With the real data. (bites lip)
Really want to try the SharePoint restore-to-new-location technique, especially because we need a development environment with the same security and config settings as the original. Apparently, while not synced, this is a common way to establish a dev environment.
Rumor has it, however, that attempts to do so in our setup have not succeeded, due to name conflicts? Hmmm, we have a meeting next week with the original admin. I’ll keep you posted.