Syncback leverages Volume Shadow Copy service (VSS)and SQL Server's VSS Writer. The standard version can be used for this purpose (called by a SQL Agent job). The free version is not licensed for commercial use (only the freeware utilities are licensed for that purpose). Only the paid version of Syncback will back up the system DB files while SQL Server is running. Here is what I have learned, followed by a question I am seeking input on. I am experimenting with Syncback as a tool for creating the copies of the system files. So, my objective is to create an automated process for creating these copies, driven by a SQL Agent job that polls for changes in the build level. I know that the safest way to do this is to manually shut down SQL Server long enought to make the copies, but shutting down SQL Server can cause application outages, and is prone to human error (forgetting to do it after applying a patch). This copy needs to be from the current build of SQL Server that is on that Windows server, but can be as old as the last date that a patch was applied to that instance of SQL Server My strategy is to maintain a copy of the system database files elsewhere on the server - a copy that will be backed up onto tape along with the rest of the server files (because the copy is not being held open). I would like to avoid having to re-install SQL Server or run the setup REBUILD option to get past this problem. There are local disk backups of the system databases sitting on the disk, but SQL server cannot be started, so the backups cannot be restored. Our TSM tape backup system skips open MDF and LDF files, so after a server has been recovered, the SQL Server system database files are missing. My question is this:ĭo I need to worry about negative impacts on the server's performance or consumption of disk space by VSS if there are other large data or log files existing on the same volume as the system database files? This posting is focused on using SnycBack as a tool for creating local copies of the system databases for recovery purposes.
0 Comments
Leave a Reply. |