UNSOLVED
J
jessehouwing1
4 Posts
0
1364
January 20th, 2014 04:00
Configuring Networker to backup multiple TFS databases using Transaction markers
As a TFS consultant I've come in contact with an organisation that is using EMC Networker to backup their SQL Server databases. They've also configured EMC to backup their SQL Server databases that hold the data to their TFS environment.
However, as TFS requires that multiple databases are backup up together, there's normally an extensive process to set up the backup correctly. The process includes setting up a special backup job that creates a set of Transaction Markers in the different SQL databases that make up the TFS dataset and then backs up the databases. This is the same procedure you'd use to backup SharePoint databases if you were doing standard backups.
How do we setup Networker to backup these databases properly? My backup operator has never setup a database this way...
In short what we need is for Networker to call the procedure to drop the markers and then backup the databases.
I believe when they refer to markers they are referring that each DB should be backed up at the same time so that you don't get sync errors later on during restore and init of the TFS. Do you use also SP component (as for that NMM should be used as it supports such approach over SP).
jessehouwing1
4 Posts
819
0
Posted January 20th, 2014 04:00
That's kind of what it means. Since databases can't be backup up at the same time by default (using standard backup features of SQL Server), this procedure creates a set of special tables where the "high water mark" is stored. This is later used to recover up to a specific point in the transaction logs.
If there is a different process to be followed when using Networker, then I'd love to read about it, since there is no public documentation anywhere...
jessehouwing1
4 Posts
819
0
Posted January 20th, 2014 05:00
Looking at the docs for NMM 3.0sp1 I see that there is no support for databases in anything other than Simple Recovery and I see no options to ensure backups are done in the correct order or after creating a marker. This seems to conflict with the way the Microsoft docs mention how to do it. Has anyone here setup a TFS backup and can walk me through tthe process?
The system looks like:
SQL Server (2012sp1)
- TFS_Configuration
- TFS_Warehouse
- TFS_Analysis (Analysis Services)
- ReportServer
- ReportServer_TempDB
- 1 or more TFS_#####Collection (where ##### is the collectionname)
In the future we might add additional SQL Server databases that can host additional TFS_#####Collection databases.
All of these databases must be in sync when the backup is made. The procedure with the markers is designed to help do that.
If stored procedure is SQL one and you wish to execute it before backup kicks in, one way of doing it is to run pre-command. I do not use that with NMM so I do not know if this is possible or not - check if documentation has anything on it.
jessehouwing1
4 Posts
819
0
Posted January 20th, 2014 06:00
Which brings me back to how I configure it in combination with EMC calling the required stored procedure before issuing the backup command to the SQL Server database.
Quick check didn't reveal pre/post commands with VDI. What I would suggest is that you:
- configure DB backup using VDI for each database using exactly the same schedule and time execution
- configure TLOG backup
- run this
- do test restore
- verify no sync issues are seen
ble1
6 Operator
•
14354 Posts
•
56186 Points
819
1
Posted January 20th, 2014 04:00
You can find documentation at support.emc.com - as your organisation has product, I'm quite sure they have access as well.
One idea is to schedule DB backup at the same time - in theory that should work fine, but should be tested. Another approach is, if you use SP components, to utilize SP backup approach as discussed in NMM documentation.