{"id":4394,"date":"2013-06-05T13:39:46","date_gmt":"2013-06-05T12:39:46","guid":{"rendered":"http:\/\/blog.capdata.fr\/?p=4394"},"modified":"2019-09-13T14:06:38","modified_gmt":"2019-09-13T13:06:38","slug":"reclusteriser-une-instance-standalone","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/","title":{"rendered":"Reclusteriser une instance standalone"},"content":{"rendered":"<a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-twitter nolightbox\" data-provider=\"twitter\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Twitter\" href=\"https:\/\/twitter.com\/intent\/tweet?url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F4394&#038;text=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"twitter\" title=\"Share on Twitter\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-linkedin nolightbox\" data-provider=\"linkedin\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Linkedin\" href=\"https:\/\/www.linkedin.com\/shareArticle?mini=true&#038;url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F4394&#038;title=Reclusteriser%20une%20instance%20standalone\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"linkedin\" title=\"Share on Linkedin\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-mail nolightbox\" data-provider=\"mail\" rel=\"nofollow\" title=\"Share by email\" href=\"mailto:?subject=Reclusteriser%20une%20instance%20standalone&#038;body=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20:%20https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F4394\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"mail\" title=\"Share by email\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" \/><\/a><p>C&#8217;est arriv\u00e9 pr\u00e8s de chez vous: un upgrade de cluster SQL Server 2008 R2 vers 2012 qui passe de travers et qui sort en erreur. Au final, l&#8217;instance clusteris\u00e9e ne d\u00e9marre plus, le service est indisponible. Rechercher les causes du probl\u00e8me initial prendra trop de temps et il faut remonter le service en ligne le plus vite possible. L&#8217;instance est donc r\u00e9install\u00e9e en standalone sur un des anciens n\u0153uds du cluster, les volumes remont\u00e9s, les bases rattach\u00e9es, et le service peut repartir.<\/p>\n<p>La question : comment revenir \u00e0 la situation de d\u00e9part et reclusteriser cette instance ?<\/p>\n<h2>Situation de d\u00e9part:<\/h2>\n<p>Il n&#8217;y a pas de recette magique, pas d&#8217;assistant pour reclusteriser une instance standalone, parce que les fonctionnalit\u00e9s cluster doivent \u00eatre install\u00e9es avant SQL Server, et que l&#8217;install de SQL Server en cluster est une installation tr\u00e8s diff\u00e9rente d&#8217;une installation standalone. Nous voici donc \u00e0 notre point de d\u00e9part&#8230;<\/p>\n<p>La machine SQLN1 est la machine qui a \u00e9t\u00e9 remont\u00e9e en standalone. Elle est enregistr\u00e9e dans le domaine et le SQL Server qui a \u00e9t\u00e9 remont\u00e9 a r\u00e9cup\u00e9r\u00e9 les 2 LUNS historiques avec les fichiers de donn\u00e9es des bases. La machine SQLN2 est l&#8217;ancien noeud en \u00e9chec qui a d\u00fb \u00eatre &#8216;nettoy\u00e9&#8217; (d\u00e9sinstall SQL Server compl\u00e8te, et suppression du cluster initial). Les deux LUNS SQLDATA et SQLLOG sont aussi visibles par SQLN2, pour simplifier la d\u00e9mo, elles sont mont\u00e9es via un <a href=\"http:\/\/www.freenas.org\/\">FREENAS<\/a>:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em12.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4398\" title=\"em1\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em12.jpg\" alt=\"\" width=\"589\" height=\"508\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em12.jpg 589w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em12-300x258.jpg 300w\" sizes=\"auto, (max-width: 589px) 100vw, 589px\" \/><\/a><\/p>\n<h2>Etape 1: recr\u00e9er un cluster \u00e0 1 n\u0153ud<\/h2>\n<p>La strat\u00e9gie va \u00eatre tout d&#8217;abord de constuire un cluster \u00e0 1 noeud sur SQLN2 avec une troisi\u00e8me LUN d&#8217;une taille juste suffisante pour mettre le r\u00e9pertoire racine de l&#8217;instance et les bases syst\u00e8mes. On partira donc avec un volume SYS de 2 Gb (LUN sqltesttemp1), et le volume de QUORUM (LUN sqltestquorum1) de l&#8217;ancien cluster qui a pu \u00eatre r\u00e9cup\u00e9r\u00e9. Avantage, on peut travailler &#8216;<em>\u00e0 c\u00f4t\u00e9<\/em>&#8216;\u00a0 de la production sans impact, en journ\u00e9e. La cible de cette premi\u00e8re \u00e9tape:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em49.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4481\" title=\"em49\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em49.png\" alt=\"\" width=\"710\" height=\"596\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em49.png 710w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em49-300x251.png 300w\" sizes=\"auto, (max-width: 710px) 100vw, 710px\" \/><\/a><\/p>\n<ul>\n<li><strong>Ajouter les features cluster + Framework 3.5SP1:<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4409\" title=\"em2\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24.jpg\" alt=\"\" width=\"540\" height=\"423\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24.jpg 540w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24-300x235.jpg 300w\" sizes=\"auto, (max-width: 540px) 100vw, 540px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4410\" title=\"em3\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32.jpg\" alt=\"\" width=\"790\" height=\"209\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32.jpg 790w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32-300x79.jpg 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32-768x203.jpg 768w\" sizes=\"auto, (max-width: 790px) 100vw, 790px\" \/><\/a><\/p>\n<ul>\n<li><strong>Pr\u00e9parer les volumes:<\/strong><\/li>\n<\/ul>\n<p>Lancer l&#8217;outil de gestion iSCSI (iscsicpl.exe), et d\u00e9clarer le portal iSCSI (dans mon cas 30.0.0.5:3260, pas d&#8217;authent CHAP):<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em4.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4413\" title=\"em4\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em4.jpg\" alt=\"\" width=\"375\" height=\"224\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em4.jpg 375w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em4-300x179.jpg 300w\" sizes=\"auto, (max-width: 375px) 100vw, 375px\" \/><\/a><\/p>\n<p>Et connecter les deux disques qui nous int\u00e9ressent: sqltestquorum1 et sqltesttemp1, via notre carte r\u00e9seau iSCSI (en 30.0.0.0\/24):<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em5.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4414\" title=\"em5\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em5.png\" alt=\"\" width=\"476\" height=\"680\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em5.png 476w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em5-210x300.png 210w\" sizes=\"auto, (max-width: 476px) 100vw, 476px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em6.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4415\" title=\"em6\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em6.png\" alt=\"\" width=\"414\" height=\"206\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em6.png 414w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em6-300x149.png 300w\" sizes=\"auto, (max-width: 414px) 100vw, 414px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em\u00e8.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4416\" title=\"em\u00e8\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em\u00e8.png\" alt=\"\" width=\"528\" height=\"618\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em\u00e8.png 528w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em\u00e8-256x300.png 256w\" sizes=\"auto, (max-width: 528px) 100vw, 528px\" \/><\/a><\/p>\n<p>Ensuite initialiser les disques (GPT) et formater avec notre cluster size de 64K. On est en Windows 2008R2, pas de probl\u00e8mes d&#8217;alignement en vue.<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em7.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4417\" title=\"em7\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em7.png\" alt=\"\" width=\"500\" height=\"380\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em7.png 500w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em7-300x228.png 300w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em8.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4418\" title=\"em8\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em8.png\" alt=\"\" width=\"499\" height=\"382\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em8.png 499w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em8-300x229.png 300w\" sizes=\"auto, (max-width: 499px) 100vw, 499px\" \/><\/a><\/p>\n<ul>\n<li><strong>Cr\u00e9er le cluster (cluadmin.msc):<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em10.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4421\" title=\"em10\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em10.png\" alt=\"\" width=\"615\" height=\"206\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em10.png 615w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em10-300x100.png 300w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/a><\/p>\n<p>Ne s\u00e9lectionner que notre n\u0153ud SQLN2 pour l&#8217;instant:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em111.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4425\" title=\"em11\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em111.png\" alt=\"\" width=\"669\" height=\"446\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em111.png 669w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em111-300x200.png 300w\" sizes=\"auto, (max-width: 669px) 100vw, 669px\" \/><\/a><\/p>\n<p>Lancer tous les tests de validation avant la cr\u00e9ation du cluster.<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em121.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4426\" title=\"em12\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em121.png\" alt=\"\" width=\"671\" height=\"444\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em121.png 671w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em121-300x198.png 300w\" sizes=\"auto, (max-width: 671px) 100vw, 671px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em132.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4428\" title=\"em13\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em132.png\" alt=\"\" width=\"671\" height=\"465\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em132.png 671w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em132-300x207.png 300w\" sizes=\"auto, (max-width: 671px) 100vw, 671px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em14.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4429\" title=\"em14\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em14.png\" alt=\"\" width=\"672\" height=\"466\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em14.png 672w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em14-300x208.png 300w\" sizes=\"auto, (max-width: 672px) 100vw, 672px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em15.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4430\" title=\"em15\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em15.png\" alt=\"\" width=\"668\" height=\"463\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em15.png 668w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em15-300x207.png 300w\" sizes=\"auto, (max-width: 668px) 100vw, 668px\" \/><\/a><\/p>\n<p>Nommer le cluster et renseigner son IP sur le LAN, dans notre cas 10.12.47.111, et terminer la cr\u00e9ation:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em16.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4431\" title=\"em16\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em16.png\" alt=\"\" width=\"671\" height=\"449\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em16.png 671w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em16-300x200.png 300w\" sizes=\"auto, (max-width: 671px) 100vw, 671px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em17.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4432\" title=\"em17\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em17.png\" alt=\"\" width=\"668\" height=\"446\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em17.png 668w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em17-300x200.png 300w\" sizes=\"auto, (max-width: 668px) 100vw, 668px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em18.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4433\" title=\"em18\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em18.png\" alt=\"\" width=\"799\" height=\"267\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em18.png 799w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em18-300x100.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em18-768x257.png 768w\" sizes=\"auto, (max-width: 799px) 100vw, 799px\" \/><\/a><\/p>\n<ul>\n<li><strong>D\u00e9clarer les disques T:\\ et Q:\\ dans le cluster:<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em21.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4435\" title=\"em21\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em21.png\" alt=\"\" width=\"246\" height=\"174\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em22.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4436\" title=\"em22\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em22.png\" alt=\"\" width=\"469\" height=\"499\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em22.png 469w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em22-282x300.png 282w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em22-281x300.png 281w\" sizes=\"auto, (max-width: 469px) 100vw, 469px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em23.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4437\" title=\"em23\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em23.png\" alt=\"\" width=\"509\" height=\"362\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em23.png 509w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em23-300x213.png 300w\" sizes=\"auto, (max-width: 509px) 100vw, 509px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<ul>\n<li><strong>Passer le quorum en node majority + Disk<\/strong> <strong>en utilisant notre disque Q:<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em19.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4438\" title=\"em19\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em19.png\" alt=\"\" width=\"574\" height=\"281\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em19.png 574w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em19-300x146.png 300w\" sizes=\"auto, (max-width: 574px) 100vw, 574px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em20.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4439\" title=\"em20\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em20.png\" alt=\"\" width=\"672\" height=\"469\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em20.png 672w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em20-300x209.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em20-250x175.png 250w\" sizes=\"auto, (max-width: 672px) 100vw, 672px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4440\" title=\"em24\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24.png\" alt=\"\" width=\"670\" height=\"467\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24.png 670w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24-300x209.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em24-250x175.png 250w\" sizes=\"auto, (max-width: 670px) 100vw, 670px\" \/><\/a><\/p>\n<p>La console avertit que dans la configuration actuelle, seul un n\u0153ud est d\u00e9clar\u00e9 et donc le quorum en tant que tel ne peut \u00eatre \u00e9tabli. Pour l&#8217;instant, c&#8217;est voulu, pas de soucis:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em25.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4441\" title=\"em25\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em25.png\" alt=\"\" width=\"494\" height=\"192\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em25.png 494w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em25-300x116.png 300w\" sizes=\"auto, (max-width: 494px) 100vw, 494px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<ul>\n<li><strong>Installer une instance SQL Server 2012 sur le noeud SQLN2:<\/strong><\/li>\n<\/ul>\n<p>Je passe sur les \u00e9tapes d&#8217;installation d&#8217;une instance sur une cluster 2008R2, voir l&#8217;<a href=\"http:\/\/conseilit.wordpress.com\/2011\/07\/18\/denali-installation-dun-cluster-2-nuds\/\">article tr\u00e8s complet<\/a> de Christophe Laporte sur le sujet. Il est juste bien important que la config du cluster ait \u00e9t\u00e9 valid\u00e9e sans quoi SQL Server ne pourra pas \u00eatre install\u00e9. Je mets juste quelques \u00e9tapes cl\u00e9s:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em26.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4445\" title=\"em26\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em26.png\" alt=\"\" width=\"815\" height=\"617\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em26.png 815w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em26-300x227.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em26-768x581.png 768w\" sizes=\"auto, (max-width: 815px) 100vw, 815px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em27.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4446\" title=\"em27\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em27.png\" alt=\"\" width=\"814\" height=\"612\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em27.png 814w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em27-300x225.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em27-768x577.png 768w\" sizes=\"auto, (max-width: 814px) 100vw, 814px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em28.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4447\" title=\"em28\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em28.png\" alt=\"\" width=\"815\" height=\"610\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em28.png 815w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em28-300x224.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em28-768x575.png 768w\" sizes=\"auto, (max-width: 815px) 100vw, 815px\" \/><\/a><\/p>\n<p>Le SQL Network Name pointera vers l&#8217;IP 10.12.47.110:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em29.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4448\" title=\"em29\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em29.png\" alt=\"\" width=\"818\" height=\"611\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em29.png 818w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em29-300x224.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em29-768x574.png 768w\" sizes=\"auto, (max-width: 818px) 100vw, 818px\" \/><\/a><\/p>\n<p>On met tout sous le T:\\ pour l&#8217;instant, la situation est temporaire jusqu&#8217;\u00e0 la bascule sur les autres volumes:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em31.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4450\" title=\"em31\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em31.png\" alt=\"\" width=\"818\" height=\"604\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em31.png 818w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em31-300x221.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em31-768x567.png 768w\" sizes=\"auto, (max-width: 818px) 100vw, 818px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4455\" title=\"em32\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32.png\" alt=\"\" width=\"816\" height=\"612\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32.png 816w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32-300x225.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em32-768x576.png 768w\" sizes=\"auto, (max-width: 816px) 100vw, 816px\" \/><\/a><\/p>\n<h2>Etape 2: rattacher les volumes de l&#8217;instance standalone \u00e0 l&#8217;instance clusteris\u00e9e.<\/h2>\n<p>C&#8217;est l&#8217;\u00e9tape d\u00e9licate. Elle n\u00e9cessite une coupure des services et de l&#8217;instance sur SQLN1. La man\u0153uvre consiste \u00e0 d\u00e9connecter les volumes de SQLN1 une fois l&#8217;instance stopp\u00e9e, et les reconnecter sur SQLN2, puis remplacer les bases syst\u00e8mes par celles provenant de SQLN1. Comme SQLN1 est une instance standalone, les bases syst\u00e8mes se trouvent sur un disque local. Il faudra donc les d\u00e9placer sur un des disques partag\u00e9s avant de basculer les volumes. On se donne rendez-vous sur le parking \u00e0 05h45, d\u00e9marrage \u00e0 06h00. Un petit caf\u00e9 et on est parti&#8230;<\/p>\n<ul>\n<li><strong>Avant faire un backup de master \/ msdb \/ model en local (\u00e7a ne co\u00fbte pas grand chose et \u00e7a peut sauver la vie)<\/strong><\/li>\n<\/ul>\n<pre name=\"code\" class=\"sql\">backup database master to disk='c:\\temp\\master_avantmigr.bak' with stats, init, compression;\r\nGO\r\nbackup database msdb to disk='c:\\temp\\msdb_avantmigr.bak' with stats, init, compression;\r\nGO\r\nbackup database model to disk='c:\\temp\\model_avantmigr.bak' with stats, init, compression;\r\nGO<\/pre>\n<ul>\n<li><strong>Arr\u00eat des applications et de l&#8217;instance sur SQLN1:<\/strong><\/li>\n<\/ul>\n<pre name=\"code\" class=\"sql\">C:\\Users\\administrator.NANTES&gt;net stop MSSQLSERVER\r\nThe following services are dependent on the SQL Server (MSSQLSERVER) service.\r\nStopping the SQL Server (MSSQLSERVER) service will also stop these services.\r\n\r\nSQL Server Agent (MSSQLSERVER)\r\n\r\nDo you want to continue this operation? (Y\/N) [N]: Y\r\nThe SQL Server Agent (MSSQLSERVER) service is stopping.\r\nThe SQL Server Agent (MSSQLSERVER) service was stopped successfully.\r\n\r\nThe SQL Server (MSSQLSERVER) service is stopping.\r\nThe SQL Server (MSSQLSERVER) service was stopped successfully.<\/pre>\n<ul>\n<li><strong>Une fois que tout est coup\u00e9, copier les fichiers MDF et LDF de master<\/strong>, <strong>msdb et model sur le drive SQLDATA.<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em48.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4480\" title=\"em48\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em48.png\" alt=\"\" width=\"792\" height=\"396\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em48.png 792w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em48-300x150.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em48-768x384.png 768w\" sizes=\"auto, (max-width: 792px) 100vw, 792px\" \/><\/a><\/p>\n<ul>\n<li><strong>Puis d\u00e9tacher les volumes de la machine SQLN1. S\u00e9lectionner les 2 volumes correspondants \u00e0 nos SQLDATA et SQLLOG, et les d\u00e9connecter depuis la machine SQLN1:<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em34.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4456\" title=\"em34\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em34.png\" alt=\"\" width=\"481\" height=\"683\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em34.png 481w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em34-211x300.png 211w\" sizes=\"auto, (max-width: 481px) 100vw, 481px\" \/><\/a><\/p>\n<ul>\n<li><strong>Ensuite les rattacher sur la machine SQLN2 de la m\u00eame mani\u00e8re, les passer online: <\/strong><\/li>\n<\/ul>\n<p><strong><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em35.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4461\" title=\"em35\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em35.png\" alt=\"\" width=\"480\" height=\"676\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em35.png 480w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em35-213x300.png 213w\" sizes=\"auto, (max-width: 480px) 100vw, 480px\" \/><\/a><\/strong><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em361.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4463\" title=\"em36\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em361.png\" alt=\"\" width=\"930\" height=\"174\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em361.png 930w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em361-300x56.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em361-768x144.png 768w\" sizes=\"auto, (max-width: 930px) 100vw, 930px\" \/><\/a><\/p>\n<ul>\n<li><strong>\u00a0et les ajouter comme ressource de stockage au cluster:<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em38.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4465\" title=\"em38\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em38.png\" alt=\"\" width=\"466\" height=\"495\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em38.png 466w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em38-282x300.png 282w\" sizes=\"auto, (max-width: 466px) 100vw, 466px\" \/><\/a><\/p>\n<ul>\n<li><strong>Il faut aussi v\u00e9rifier que les lettres sont bien respect\u00e9es E: pour SQLDATA, et L: pour SQLLOG.<\/strong><\/li>\n<\/ul>\n<p>Si ce n&#8217;est pas le cas, il faut renommer la lettre via la console d&#8217;administration du cluster:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em52.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4487\" title=\"em52\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em52.png\" alt=\"\" width=\"378\" height=\"263\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em52.png 378w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em52-300x208.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em52-250x175.png 250w\" sizes=\"auto, (max-width: 378px) 100vw, 378px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em53.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4488\" title=\"em53\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em53.png\" alt=\"\" width=\"262\" height=\"132\" \/><\/a><\/p>\n<p>A partir de l\u00e0, on va devoir stopper l&#8217;instance sur SQLN2, pour rattacher les nouveaux disques au groupe de ressources SQL Server, refaire les d\u00e9pendances, ajouter MSDTC, et red\u00e9poser nos bases syst\u00e8mes \u00e0 la place des anciennes sur le T:\\<\/p>\n<ul>\n<li><strong>On stoppe SQL Server sur SQLN2 (en utilisant la console du cluster ! ):<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em39.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4467\" title=\"em39\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em39.png\" alt=\"\" width=\"470\" height=\"408\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em39.png 470w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em39-300x260.png 300w\" sizes=\"auto, (max-width: 470px) 100vw, 470px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em40.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4468\" title=\"em40\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em40.png\" alt=\"\" width=\"443\" height=\"253\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em40.png 443w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em40-300x171.png 300w\" sizes=\"auto, (max-width: 443px) 100vw, 443px\" \/><\/a><\/p>\n<ul>\n<li><strong>On rattache les deux nouveaux volumes au groupe de ressources SQL Server (refaire la manip pour chaque disque):<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em41.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4469\" title=\"em41\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em41.png\" alt=\"\" width=\"592\" height=\"377\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em41.png 592w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em41-300x191.png 300w\" sizes=\"auto, (max-width: 592px) 100vw, 592px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em42.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4470\" title=\"em42\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em42.png\" alt=\"\" width=\"586\" height=\"360\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em42.png 586w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em42-300x184.png 300w\" sizes=\"auto, (max-width: 586px) 100vw, 586px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<ul>\n<li><strong>On modifie les d\u00e9pendances disque de SQL Server pour ajouter E: et L: <\/strong><\/li>\n<\/ul>\n<p><strong><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em50.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4482\" title=\"em50\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em50.png\" alt=\"\" width=\"400\" height=\"479\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em50.png 400w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em50-251x300.png 251w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em50-250x300.png 250w\" sizes=\"auto, (max-width: 400px) 100vw, 400px\" \/><\/a><\/strong><\/p>\n<p>&nbsp;<\/p>\n<ul>\n<li><strong>On ajoute notre MSDTC, qui va d\u00e9pendre d&#8217;un disque + du nom r\u00e9seau, et le passer online:<\/strong><\/li>\n<\/ul>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em44.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4473\" title=\"em44\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em44.png\" alt=\"\" width=\"808\" height=\"494\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em44.png 808w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em44-300x183.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em44-768x470.png 768w\" sizes=\"auto, (max-width: 808px) 100vw, 808px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em45.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4474\" title=\"em45\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em45.png\" alt=\"\" width=\"402\" height=\"478\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em45.png 402w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em45-252x300.png 252w\" sizes=\"auto, (max-width: 402px) 100vw, 402px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em46.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4475\" title=\"em46\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em46.png\" alt=\"\" width=\"472\" height=\"323\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em46.png 472w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em46-300x205.png 300w\" sizes=\"auto, (max-width: 472px) 100vw, 472px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<ul>\n<li><strong>On va ensuite recopier les fichiers de donn\u00e9es de master, msdb et model sur les fichiers dans l\u2019arborescence attendue sous le T:\\ (optionnel pour model)<\/strong><\/li>\n<\/ul>\n<p>Par pr\u00e9caution on va renommer les anciens fichiers en _old:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em51.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4483\" title=\"em51\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em51.png\" alt=\"\" width=\"525\" height=\"363\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em51.png 525w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em51-300x207.png 300w\" sizes=\"auto, (max-width: 525px) 100vw, 525px\" \/><\/a><\/p>\n<ul>\n<li><strong>Modifier les chemins d&#8217;acc\u00e8s \u00e0 MSDB et model, en d\u00e9marrant en mode master recovery only:<\/strong><\/li>\n<\/ul>\n<p>En effet, les anciennes bases syst\u00e8mes \u00e9taient stock\u00e9es sous le C:\\Program Files\\&#8230;\u00a0 sur l&#8217;ancienne instance. Le chemin de master est ok (sur le T:\\), mais les chemins de msdb et model pointent toujours vers le C:\\ et sont grav\u00e9s dans master.mdf. L&#8217;instance ne pouvant pas d\u00e9marrer sans model \u00e0 cause de tempdb, il faut passer par cette \u00e9tape en d\u00e9marrant l&#8217;instance avec le <a href=\"http:\/\/msdn.microsoft.com\/en-us\/library\/ms188396.aspx\">traceflag -T3608<\/a>.<\/p>\n<p>Attention il y a une autre astuce, car par d\u00e9faut SQL Server associe -T3608 avec le mode single-user. Mais dans un cluster, la premi\u00e8re connexion est utilis\u00e9e par la dll qui contr\u00f4le l&#8217;\u00e9tat de la ressource (<a href=\"http:\/\/msdn.microsoft.com\/en-us\/library\/ms188236.aspx\">ref<\/a>), donc il faut d\u00e9marrer via le service en shuntant la console du cluster :<\/p>\n<pre name=\"code\" class=\"sql\">C:\\Users\\administrator.NANTES&gt;net start MSSQLSERVER \/t3608\r\nThe SQL Server (MSSQLSERVER) service is starting.\r\nThe SQL Server (MSSQLSERVER) service was started successfully.<\/pre>\n<p>On se connecte et on modifie d&#8217;abord msdb:<\/p>\n<pre name=\"code\" class=\"sql\">C:\\Users\\administrator.NANTES&gt;sqlcmd -E -S SQLTEST\r\n1> select name from sys.master_files where database_id = db_id('msdb')\r\n2> go\r\nname\r\n--------------------------------------------------------------------------------------------------------------------------------\r\nMSDBData\r\nMSDBLog\r\n\r\n1> alter database msdb modify file (name='MSDBData',filename='T:\\MSSQL11.MSSQLSERVER\\MSSQL\\DATA\\MSDBData.mdf')\r\n2> alter database msdb modify file (name='MSDBLog',filename='T:\\MSSQL11.MSSQLSERVER\\MSSQL\\DATA\\MSDBLog.ldf')\r\n3> go\r\nThe file \"MSDBData\" has been modified in the system catalog. The new path will be used the next time the database is started.\r\nThe file \"MSDBLog\" has been modified in the system catalog. The new path will be used the next time the database is started.<\/pre>\n<p>Puis model:<\/p>\n<pre name=\"code\" class=\"sql\">1> select name from sys.master_files where database_id = db_id('model')\r\n2> go\r\nname\r\n--------------------------------------------------------------------------------------------------------------------------------\r\nmodeldev\r\nmodellog\r\n\r\n(2 rows affected)\r\n1> alter database model modify file (name='modeldev',filename='T:\\MSSQL11.MSSQLSERVER\\MSSQL\\DATA\\model.mdf')\r\n2> alter database model modify file (name='modellog',filename='T:\\MSSQL11.MSSQLSERVER\\MSSQL\\DATA\\modellog.ldf')\r\n3> go\r\nThe file \"modeldev\" has been modified in the system catalog. The new path will be used the next time the database is started.\r\nThe file \"modellog\" has been modified in the system catalog. The new path will be used the next time the database is started.<\/pre>\n<p>Puis on stoppe et on relance l&#8217;instance en repassant la ressource en ligne:<\/p>\n<pre name=\"code\" class=\"sql\">C:\\Users\\administrator.NANTES&gt;net stop MSSQLSERVER\r\nThe SQL Server (MSSQLSERVER) service is stopping.\r\nThe SQL Server (MSSQLSERVER) service was stopped successfully.<\/pre>\n<p>&nbsp;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em541.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4490\" title=\"em54\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em541.png\" alt=\"\" width=\"475\" height=\"434\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em541.png 475w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em541-300x274.png 300w\" sizes=\"auto, (max-width: 475px) 100vw, 475px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>On se connecte et on v\u00e9rifie qu&#8217;on a bien r\u00e9cup\u00e9r\u00e9 tous nos petits &#8230; (bases, logins, jobs, plans de maintenance)&#8230;<\/p>\n<p><strong>=&gt; Et on relance les applications<\/strong> !!<\/p>\n<p>Il reste \u00e0 faire un peu de nettoyage : l&#8217;ancienne tempdb potentiellement, et les fichiers _old des bases master, msdb et model. Et voil\u00e0. On a r\u00e9cup\u00e9r\u00e9 notre prod sur un cluster \u00e0 1 n\u0153ud.<\/p>\n<h2>Etape 3: ajouter le second n\u0153ud au cluster.<\/h2>\n<p>Bon apr\u00e8s &#8211; et bien que je sois en partie d&#8217;accord avec mon camarade MVP Linchi Shea (voir <a href=\"http:\/\/sqlblog.com\/blogs\/linchi_shea\/archive\/2012\/02\/10\/clustering-every-sql-server-instance.aspx\">article<\/a>) &#8211; un cluster \u00e0 un noeud n&#8217;a pas beaucoup d&#8217;int\u00e9r\u00eat en soi. La derni\u00e8re partie, qui elle aussi peut se faire \u00e0 chaud, consiste \u00e0 int\u00e9grer l&#8217;ancienne machine standalone comme second noeud du cluster. Par rapport \u00e0 ce qu&#8217;on vient de faire, du tourisme quoi&#8230;<\/p>\n<p>La cible une fois l&#8217;op\u00e9ration termin\u00e9e:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em55.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4494\" title=\"em5(\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em55.png\" alt=\"\" width=\"610\" height=\"590\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em55.png 610w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em55-300x290.png 300w\" sizes=\"auto, (max-width: 610px) 100vw, 610px\" \/><\/a><\/p>\n<p>Comme SQLN1 est un ancien n\u0153ud de cluster, les features (.NET 3.5SP1 + cluster) sont d\u00e9j\u00e0 l\u00e0, pas la peine de les r\u00e9installer. Il faut d\u00e9sinstaller par contre tout ce qui a attrait \u00e0 SQL Server, on va repartir d&#8217;une machine &#8216;<em>clean<\/em>&#8216;: (on peut laisser les runtimes vc++):<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em57.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4496\" title=\"em57\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em57.png\" alt=\"\" width=\"708\" height=\"502\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em57.png 708w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em57-300x212.png 300w\" sizes=\"auto, (max-width: 708px) 100vw, 708px\" \/><\/a><\/p>\n<p>Ensuite il faut reconnecter les 4 disques clusteris\u00e9s en utilisant iscsicpl:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em70.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4518\" title=\"em70\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em70.png\" alt=\"\" width=\"485\" height=\"668\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em70.png 485w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em70-218x300.png 218w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em70-217x300.png 217w\" sizes=\"auto, (max-width: 485px) 100vw, 485px\" \/><\/a><\/p>\n<p>Une fois la machine nettoy\u00e9e et les disques reconnect\u00e9s, on va la rajouter comme n\u0153ud \u00e0 notre cluster:<a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em59.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4501\" title=\"em59\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em59.png\" alt=\"\" width=\"262\" height=\"222\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em60.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4502\" title=\"em60\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em60.png\" alt=\"\" width=\"677\" height=\"466\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em60.png 677w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em60-300x206.png 300w\" sizes=\"auto, (max-width: 677px) 100vw, 677px\" \/><\/a><\/p>\n<p>Lancer la validation mais \u00e9videmment <strong><span style=\"text-decoration: underline;\">laisser le groupe de ressources SQL Server online<\/span> <\/strong>pendant les tests, sinon le t\u00e9l\u00e9phone risque de sonner rapidement&#8230;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em61.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4503\" title=\"em61\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em61.png\" alt=\"\" width=\"669\" height=\"465\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em61.png 669w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em61-300x208.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em61-250x175.png 250w\" sizes=\"auto, (max-width: 669px) 100vw, 669px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>Quelques warnings seront g\u00e9n\u00e9r\u00e9s dans la mesure o\u00f9 les disques n&#8217;ont pas pu \u00eatre mis hors-ligne pour faire les tests. Pas de soucis. On retrouvera les m\u00eames warnings lors de l&#8217;installation du second SQL Server clusteris\u00e9. Et sinon un avertissement pour nous indiquer toutefois que les ressources SQL Server \/ SQL Agent, etc&#8230; ne sont pas d\u00e9clar\u00e9es sur le second donc une bascule n&#8217;est pas encore possible. On y arrive&#8230;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em62.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4506\" title=\"em62\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em62.png\" alt=\"\" width=\"671\" height=\"467\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em62.png 671w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em62-300x208.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em62-250x175.png 250w\" sizes=\"auto, (max-width: 671px) 100vw, 671px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em63.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4507\" title=\"em63\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em63.png\" alt=\"\" width=\"675\" height=\"465\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em63.png 675w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em63-300x206.png 300w\" sizes=\"auto, (max-width: 675px) 100vw, 675px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em64.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4508\" title=\"em64\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em64.png\" alt=\"\" width=\"285\" height=\"222\" \/><\/a><\/p>\n<p>A cette \u00e9tape, il faut aussi penser \u00e0 autoriser le nouveau noeud SQLN1 \u00e0 pouvoir poss\u00e9der les disques clusteris\u00e9s d\u00e9clar\u00e9s, donc dans les propri\u00e9t\u00e9s de chaque disque sous &#8216;storage&#8217;, Advanced Policies, il faut cocher SQLN1:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em681.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4515\" title=\"em68\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em681.png\" alt=\"\" width=\"401\" height=\"481\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em681.png 401w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em681-250x300.png 250w\" sizes=\"auto, (max-width: 401px) 100vw, 401px\" \/><\/a><\/p>\n<p>On a donc enfin notre second n\u0153ud vierge dans le cluster. Sur SQLN1, lancer l&#8217;install du second n\u0153ud SQL Server:<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em581.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4497\" title=\"em58\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em581.png\" alt=\"\" width=\"790\" height=\"270\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em581.png 790w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em581-300x102.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em581-768x262.png 768w\" sizes=\"auto, (max-width: 790px) 100vw, 790px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em65.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4509\" title=\"em65\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em65.png\" alt=\"\" width=\"816\" height=\"610\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em65.png 816w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em65-300x224.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em65-768x574.png 768w\" sizes=\"auto, (max-width: 816px) 100vw, 816px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em661.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4512\" title=\"em66\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em661.png\" alt=\"\" width=\"817\" height=\"612\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em661.png 817w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em661-300x224.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em661-768x575.png 768w\" sizes=\"auto, (max-width: 817px) 100vw, 817px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em67.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4513\" title=\"em67\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em67.png\" alt=\"\" width=\"816\" height=\"611\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em67.png 816w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em67-300x224.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em67-768x575.png 768w\" sizes=\"auto, (max-width: 816px) 100vw, 816px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em69.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4516\" title=\"em69\" src=\"http:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em69.png\" alt=\"\" width=\"818\" height=\"610\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em69.png 818w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em69-300x223.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em69-768x573.png 768w\" sizes=\"auto, (max-width: 818px) 100vw, 818px\" \/><\/a><\/p>\n<p>&nbsp;<br \/>\nEt bien s\u00fbr tester une bascule en heures non ouvr\u00e9es pour valider le retour en nominal. Attention, lors du test de bascule, il est extr\u00eamement important d&#8217;avoir bien le m\u00eame build de chaque c\u00f4t\u00e9, sans quoi si la version est sup\u00e9rieure sur le n\u0153ud sur lequel on va basculer, les bases vont passer en script upgrade, et selon la volum\u00e9trie \u00e7a peut durer un certain temps avant qu&#8217;elles ne soient mises online (1 heure de script upgrade pour une base de 2.3Tb \u00e0 titre d&#8217;exemple).<\/p>\n<p>Allez record de screenshots battu. A+ David B.<\/p>\n<p>&nbsp;<\/p>\n<a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-twitter nolightbox\" data-provider=\"twitter\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Twitter\" href=\"https:\/\/twitter.com\/intent\/tweet?url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F4394&#038;text=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"twitter\" title=\"Share on Twitter\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-linkedin nolightbox\" data-provider=\"linkedin\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Linkedin\" href=\"https:\/\/www.linkedin.com\/shareArticle?mini=true&#038;url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F4394&#038;title=Reclusteriser%20une%20instance%20standalone\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"linkedin\" title=\"Share on Linkedin\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-mail nolightbox\" data-provider=\"mail\" rel=\"nofollow\" title=\"Share by email\" href=\"mailto:?subject=Reclusteriser%20une%20instance%20standalone&#038;body=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20:%20https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F4394\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"mail\" title=\"Share by email\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" \/><\/a>","protected":false},"excerpt":{"rendered":"<p>C&#8217;est arriv\u00e9 pr\u00e8s de chez vous: un upgrade de cluster SQL Server 2008 R2 vers 2012 qui passe de travers et qui sort en erreur. Au final, l&#8217;instance clusteris\u00e9e ne d\u00e9marre plus, le service est indisponible. Rechercher les causes du&hellip; <a href=\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/\" class=\"more-link\">Continuer la lecture <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":4396,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[21],"class_list":["post-4394","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sqlserver","tag-cluster"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Reclusteriser une instance standalone - Capdata TECH BLOG<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Reclusteriser une instance standalone - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"C&#8217;est arriv\u00e9 pr\u00e8s de chez vous: un upgrade de cluster SQL Server 2008 R2 vers 2012 qui passe de travers et qui sort en erreur. Au final, l&#8217;instance clusteris\u00e9e ne d\u00e9marre plus, le service est indisponible. Rechercher les causes du&hellip; Continuer la lecture &rarr;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2013-06-05T12:39:46+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-09-13T13:06:38+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"589\" \/>\n\t<meta property=\"og:image:height\" content=\"508\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"David Baffaleuf\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Baffaleuf\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/\"},\"author\":{\"name\":\"David Baffaleuf\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf\"},\"headline\":\"Reclusteriser une instance standalone\",\"datePublished\":\"2013-06-05T12:39:46+00:00\",\"dateModified\":\"2019-09-13T13:06:38+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/\"},\"wordCount\":1669,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"keywords\":[\"cluster\"],\"articleSection\":[\"SQL Server\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/\",\"name\":\"Reclusteriser une instance standalone - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2013-06-05T12:39:46+00:00\",\"dateModified\":\"2019-09-13T13:06:38+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Reclusteriser une instance standalone\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.capdata.fr\/#website\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"name\":\"Capdata TECH BLOG\",\"description\":\"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting\",\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.capdata.fr\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.capdata.fr\/#organization\",\"name\":\"Capdata TECH BLOG\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"contentUrl\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"width\":800,\"height\":254,\"caption\":\"Capdata TECH BLOG\"},\"image\":{\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf\",\"name\":\"David Baffaleuf\",\"sameAs\":[\"http:\/\/www.capdata.fr\"],\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/dbaffaleuf\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Reclusteriser une instance standalone - Capdata TECH BLOG","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/","og_locale":"fr_FR","og_type":"article","og_title":"Reclusteriser une instance standalone - Capdata TECH BLOG","og_description":"C&#8217;est arriv\u00e9 pr\u00e8s de chez vous: un upgrade de cluster SQL Server 2008 R2 vers 2012 qui passe de travers et qui sort en erreur. Au final, l&#8217;instance clusteris\u00e9e ne d\u00e9marre plus, le service est indisponible. Rechercher les causes du&hellip; Continuer la lecture &rarr;","og_url":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2013-06-05T12:39:46+00:00","article_modified_time":"2019-09-13T13:06:38+00:00","og_image":[{"width":589,"height":508,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2013\/06\/em1.jpg","type":"image\/jpeg"}],"author":"David Baffaleuf","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"David Baffaleuf","Dur\u00e9e de lecture estim\u00e9e":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/"},"author":{"name":"David Baffaleuf","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf"},"headline":"Reclusteriser une instance standalone","datePublished":"2013-06-05T12:39:46+00:00","dateModified":"2019-09-13T13:06:38+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/"},"wordCount":1669,"commentCount":0,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"keywords":["cluster"],"articleSection":["SQL Server"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/","url":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/","name":"Reclusteriser une instance standalone - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2013-06-05T12:39:46+00:00","dateModified":"2019-09-13T13:06:38+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/reclusteriser-une-instance-standalone\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"Reclusteriser une instance standalone"}]},{"@type":"WebSite","@id":"https:\/\/blog.capdata.fr\/#website","url":"https:\/\/blog.capdata.fr\/","name":"Capdata TECH BLOG","description":"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting","publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.capdata.fr\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/blog.capdata.fr\/#organization","name":"Capdata TECH BLOG","url":"https:\/\/blog.capdata.fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/","url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","contentUrl":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","width":800,"height":254,"caption":"Capdata TECH BLOG"},"image":{"@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/"]},{"@type":"Person","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf","name":"David Baffaleuf","sameAs":["http:\/\/www.capdata.fr"],"url":"https:\/\/blog.capdata.fr\/index.php\/author\/dbaffaleuf\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/4394","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=4394"}],"version-history":[{"count":41,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/4394\/revisions"}],"predecessor-version":[{"id":4486,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/4394\/revisions\/4486"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/4396"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=4394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=4394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=4394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}