Forgot to note versions of software running.
NPM Version 12.0
NCM Version 7.4.1
NTA Version 4.1.2
OS Version on main VM Server (NPM, NCM, NTA application server) - Windows Server 2008 R2 Enterprise, Service Pack 1
OS Version on secondary VM Server (Netflow Database Configurator/Database) - Windows Server 2008 R2 Enterprise, Service Pack 1
OS Version on SQL Server - Windows Server 2008 R2 Enterprise, Service Pack 1
SQL Version on SQL Server - SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
1 of 1 people found this helpful
[late reply I know]
1. We run backups of our SQL database three times a day -- one reason I find the 'Have you saved a backup of your data' question so odd during an upgrade.
[actually we run a full backup once/day and a save the transaction logs, but same deal]
2. yes, SQLserver backups are [supposed] to be restorable. you should not have a problem with consistency between tables when restoring it.
3. I do not normally worry about stopping and starting solarwinds services over backup -- they don't know/notice that the transactions are only hitting the log, not the actual database during the backup window. nor should they.
You can also drop an "app_offline.htm" file into your solarwinds inetpub directory, and the server will serve that up instead of an error page.
We have a pair of database servers mirroring data between them, so during maintenance on one server we switch over to the other server.
Mirrored databases running in full recovery used to give solarwinds support conniptions and they point at our DB every time...except our DB servers are an identical pair of high-performance servers with over 24 spindles in the arrays rather than the common situation of the backupserver being woefully underpowered. [these servers are 6 years old now, due for replacement in the next FY -- PCIe SSD are now a cost-optimal choice for the database]
Personally, as I do not see that anything bad would happen: I'd drop the app_offline.htm file in there
then the maintenance happens without
remove the app_offline file
see what broke
[open a support case if anything did break, because services should all recover if the database connectivity gets lost/broken anyway.]
restart all of the Solarwinds Services to make sure