sbrassard Posted January 5, 2012 Report Share Posted January 5, 2012 My team and I recently migrated from VSS to PlasticSCM and all has gone well. We decided not to pull anything but the latest version from VSS into Plastic to start from a "clean slate". If we need history on something we can always use VSS. Anyways, my question has to do with PlasticSCM and SQLServer. Can someone tell me what specifically needs to get backed up when using PlasticSCM and SQLServer to ensure we don't lose any code. Thanks Link to comment Share on other sites More sharing options...
cidico Posted January 5, 2012 Report Share Posted January 5, 2012 I believe that all that you need to do is keep the database server backed up. Or, if you want just to backup the plastic databases, the repositories databases inside an instance of sql server. I believe that the database names has the same strategy that SQL Server CE has.. using repository_1.plastic ... Link to comment Share on other sites More sharing options...
manu Posted January 9, 2012 Report Share Posted January 9, 2012 Hi sbrassard, you can schedule databases backups at SQLServer level as cidico says, you need to backup the "repositories" db and all your "rep_XYZ" db's. You can also have a mirrored PlasticSCM server and every night replicate all the new content from your working server to your mirrored server. Manu. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.