I've built an instance of Artifactory utilizing MS SQL as a database backend; storage setting 'fullDB'(both metadata and artifact BLOBs). I've chosen the full storage SQL backend in an attempt to provide a 'stateless' Artifactory instance. I'm hoping for the ability to delete or lose the 'current’ Artifactory instance, then re-provision and rely on configuration management to build a new VM and attach it to the existing MS SQL instance.
However in my testing when attaching the newly provisioned Artifactory instance to the existing MS SQL DB, I'm not seeing the previous VM's repos in the Artifact Repository Browser. When looking in the ’Storage' section of the Advanced Admin console I see the previous repos in the Storage Summary with Repository Type and Package Type value of ’NA’. So it’s as though the storage does see the repo but cannot identify the appropriate metadata. No Artifactory version change occurred between the two different builds. Is it possible to attach a new instance of Artifactory to an existing fullDB instance as a means of host migration? -- View this message in context: http://forums.jfrog.org/New-Artifactory-host-w-existing-fullDB-MS-SQL-instance-tp7580825.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
