{"id":9481,"date":"2022-11-14T15:16:24","date_gmt":"2022-11-14T14:16:24","guid":{"rendered":"https:\/\/blog.capdata.fr\/?p=9481"},"modified":"2023-01-19T11:28:37","modified_gmt":"2023-01-19T10:28:37","slug":"redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/","title":{"rendered":"Red\u00e9marrage des serveurs par l&#8217;hyperviseur : \u00e7a fait mal ?"},"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%2F9481&#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%2F9481&#038;title=Red%C3%A9marrage%20des%20serveurs%20par%20l%E2%80%99hyperviseur%20%3A%20%C3%A7a%20fait%20mal%20%3F\" 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=Red%C3%A9marrage%20des%20serveurs%20par%20l%E2%80%99hyperviseur%20%3A%20%C3%A7a%20fait%20mal%20%3F&#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%2F9481\" 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>Avec la virtualisation, on trouve de plus en plus d&#8217;op\u00e9rations de red\u00e9marrages plus agressifs que les op\u00e9rations de maintenances plus classiques. En effet, il y a parfois des op\u00e9rations de bascules de VM entre h\u00f4tes, de la maintenance sur des SAN ou autre, et cela peut pousser \u00e0 des red\u00e9marrages sans tenir compte de ce qui se passe sur le serveur. Et c&#8217;est souvent la nuit&#8230; pendant les phases de batchs !<\/p>\n<p>Mais quel est l&#8217;impact ? Est-ce que SQL Server est r\u00e9silient \u00e0 ces actions ? Quels sont les risques ?<\/p>\n<p>&nbsp;<\/p>\n<p>Pour r\u00e9pondre \u00e0 cette question en version courte, utilisons en maquette un SQL Server 2019 sur une petite VM 2 vCPU \/\u00a0 4 Go de RAM (B2S dans Azure). Dessus, une base de donn\u00e9es d&#8217;exemple de Stack Overflow de 50 Go.<\/p>\n<p>Le protocole de test est le suivant :<\/p>\n<ul>\n<li>r\u00e9alisation d&#8217;une instruction<\/li>\n<li>Arr\u00eat de la VM par Azure \/ Kill du processus sqlserver.exe<\/li>\n<li>Observation des logs apr\u00e8s red\u00e9marrage de SQL Server<\/li>\n<\/ul>\n<h1>Manipulation d&#8217;index :<\/h1>\n<p>Si on r\u00e9alise une op\u00e9ration de type drop d&#8217;index \/ cr\u00e9ation d&#8217;index : le temps de r\u00e9cup\u00e9ration est n\u00e9gligeable. En effet, la structure nouvellement cr\u00e9\u00e9e l&#8217;est en parall\u00e8le d&#8217;une existante. Par exemple le drop d&#8217;un clustered index cr\u00e9\u00e9 un heap en parall\u00e8le et \u00e0 la fin, le heap est drop\u00e9. Pour la cr\u00e9ation d&#8217;un clustered index, c&#8217;est la m\u00eame chose. Pour l&#8217;ajout ou le drop d&#8217;un index classique, il s&#8217;agit d&#8217;une structure suppl\u00e9mentaire qui repose sur le heap ou le clustered index, donc encore moins d&#8217;inqui\u00e9tude.<\/p>\n<p>Le red\u00e9marrage lors de ce type d&#8217;op\u00e9ration est donc sans risque majeur au moment du red\u00e9marrage.<\/p>\n<h1>Manipulation de donn\u00e9es :<\/h1>\n<p>Maintenant imaginons une op\u00e9ration qui r\u00e9alise un update massif dans une table :<\/p>\n<pre class=\"brush: sql; title: ; notranslate\" title=\"\">UPDATE Posts\r\nSET AnswerCount = AnswerCount + 1 <\/pre>\n<p>Si on laisse tourner la requ\u00eate pendant 30 secondes puis qu&#8217;on tue la machine ou le processus, puis que l&#8217;on red\u00e9marre, on verra dans les logs :<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-9483\" src=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_petit_recovery-300x105.png\" alt=\"\" width=\"1377\" height=\"482\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_petit_recovery-300x105.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_petit_recovery-1024x358.png 1024w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_petit_recovery-768x269.png 768w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_petit_recovery.png 1360w\" sizes=\"auto, (max-width: 1377px) 100vw, 1377px\" \/><\/p>\n<p>La reprise de la base a donc pris 43 secondes.<\/p>\n<p>R\u00e9alisons la m\u00eame op\u00e9ration mais en la laissant tourner la requ\u00eate 5 minutes :<\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-9482\" src=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_gros_recovery-300x190.png\" alt=\"\" width=\"1467\" height=\"929\" srcset=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_gros_recovery-300x190.png 300w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_gros_recovery-1024x649.png 1024w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_gros_recovery-768x487.png 768w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_gros_recovery-1536x974.png 1536w, https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/logs_gros_recovery.png 1708w\" sizes=\"auto, (max-width: 1467px) 100vw, 1467px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Le red\u00e9marrage a mis cette fois 1 019 secondes pour faire la r\u00e9cup\u00e9ration de cette base ! Par ailleurs, on voit dans les logs des avertissements sur les temps de r\u00e9ponse du disque (il s&#8217;agit d&#8217;une petite VM) : cela indique que la VM est vraiment tr\u00e8s tr\u00e8s sollicit\u00e9e niveau IO. Si on avait un vrai serveur de production avec des bases de donn\u00e9es en parall\u00e8le de celle occupant le gros recovery, les performances seraient tr\u00e8s faibles (d&#8217;autant + avec un cache vide apr\u00e8s red\u00e9marrage).<\/p>\n<p>Et que se passe-t-il si on red\u00e9marre pendant cette phase de recovery ? Rien de particulier ! L&#8217;op\u00e9ration reprend comme elle avait eu lieu au d\u00e9marrage pr\u00e9c\u00e9dent.<\/p>\n<p>&nbsp;<\/p>\n<h1>Et \u00e7a donne quoi le &#8220;Accelerated Database Recovery&#8221; ?<\/h1>\n<p>Depuis SQL Server 2019, une fonctionnalit\u00e9 a \u00e9t\u00e9 rajout\u00e9e le &#8220;Accelerated Database Recovery&#8221; (c&#8217;est m\u00eame encore am\u00e9lior\u00e9 dans la future version 2022 !). Cette technologie, qui doit \u00eatre activ\u00e9e manuellement, permet d&#8217;am\u00e9liorer les performances de la phase de recovery (mais pas que). Il permet \u00e9galement de :<\/p>\n<ul>\n<li>Faire un rollback instantan\u00e9 d&#8217;une transaction<\/li>\n<li>R\u00e9aliser de mani\u00e8re agressive un vidage de log transactionnel (m\u00eame si une grosse transaction est en cours,\u00a0 les vieilles transactions peuvent ainsi \u00eatre purg\u00e9es).<\/li>\n<\/ul>\n<p>Il repose sur plusieurs choses :<\/p>\n<ul>\n<li>Un espace disque d\u00e9di\u00e9 \u00e0 l&#8217;int\u00e9rieur de la base sur laquelle l&#8217;ADR est activ\u00e9, appel\u00e9 Persisted Version Store (PVS). Il fait un peu penser au Version Store utilis\u00e9 dans la TempDb pour le mode Read Commited Snapshot Isolation. Cela veut dire qu&#8217;il y aura des IO suppl\u00e9mentaires et de l&#8217;espace requis \u00e0 partir du moment o\u00f9 l&#8217;ADR est activ\u00e9.<\/li>\n<li>Une zone m\u00e9moire d\u00e9di\u00e9e \u00e0 connaitre l&#8217;\u00e9tat des op\u00e9rations qui ne sont pas versionn\u00e9es dans le PVS, appel\u00e9 SLOG. Cette zone m\u00e9moire est cens\u00e9e garder une taille tr\u00e8s modeste, et est consolid\u00e9e sur disque \u00e0 chaque checkpoint. Il sert \u00e0 acc\u00e9lerer des op\u00e9rations de rollbacks et troncation du log transactionnel<\/li>\n<li>Un processus qui sert \u00e0 lire les donn\u00e9es depuis le PVS pour faire les rollbacks instantan\u00e9s : le Logical Revert<\/li>\n<li>Un processus qui sert \u00e0 \u00e0 nettoyer de mani\u00e8re asynchrone et r\u00e9guli\u00e8re les pages du PVS : le Cleaner<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>On le voit donc, c&#8217;est clairement un outil qui devrait nous permettre d&#8217;am\u00e9liorer la gestion des risques lors des red\u00e9marrages agressifs.<\/p>\n<p>&nbsp;<\/p>\n<p>Pour l&#8217;activer, il faut juste r\u00e9aliser un\u00a0 :<\/p>\n<pre class=\"brush: sql; title: ; notranslate\" title=\"\">ALTER DATABASE [DB] SET ACCELERATED_DATABASE_RECOVERY = {ON | OFF};<\/pre>\n<p>Une fois cette option activ\u00e9e sur notre base, si on r\u00e9alise le m\u00eame update, pour une dur\u00e9e de 6 minutes d&#8217;ex\u00e9cution, temps de recovery mesur\u00e9 a \u00e9t\u00e9 de &#8230; 41 secondes !<\/p>\n<p>Par ailleurs, \u00e0 partir de SQL Server 2022, le processus de recovery ne sera plus mono-thread\u00e9 et par instance, mais par base. Du moment que les performances disques suivent, le recovery sera tr\u00e8s tr\u00e8s rapide.<\/p>\n<p>&nbsp;<\/p>\n<h1>Conclusion\u00a0 :<\/h1>\n<p>Sur les versions r\u00e9centes de SQL Server, la fiabilit\u00e9 en cas de reboot\/crash\/kill lors d&#8217;une transaction est r\u00e9elle, m\u00eame avec un reboot pendant la phase de recovery. M\u00eame si cela peut durer longtemps selon la taille des transactions ainsi que selon les performances disques, la base n&#8217;est pas corrompue facilement !<\/p>\n<p>Par ailleurs, pour am\u00e9liorer ces dur\u00e9es de phases de recovery, l&#8217;ADR apport\u00e9e depuis la version 2019 apporte un gain immense. Par ailleurs, ce sont toutes les op\u00e9rations de rollbacks qui en profitent \u00e9galement.<\/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%2F9481&#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%2F9481&#038;title=Red%C3%A9marrage%20des%20serveurs%20par%20l%E2%80%99hyperviseur%20%3A%20%C3%A7a%20fait%20mal%20%3F\" 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=Red%C3%A9marrage%20des%20serveurs%20par%20l%E2%80%99hyperviseur%20%3A%20%C3%A7a%20fait%20mal%20%3F&#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%2F9481\" 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>Avec la virtualisation, on trouve de plus en plus d&#8217;op\u00e9rations de red\u00e9marrages plus agressifs que les op\u00e9rations de maintenances plus classiques. En effet, il y a parfois des op\u00e9rations de bascules de VM entre h\u00f4tes, de la maintenance sur des&hellip; <a href=\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/\" class=\"more-link\">Continuer la lecture <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":9492,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[429,430,428,427,273,425,426],"class_list":["post-9481","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sqlserver","tag-accelerated-database-recovery","tag-adr","tag-crash","tag-reboot","tag-recovery","tag-redemarrage","tag-restart"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Red\u00e9marrage des serveurs par l&#039;hyperviseur : \u00e7a fait mal ? - 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\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Red\u00e9marrage des serveurs par l&#039;hyperviseur : \u00e7a fait mal ? - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"Avec la virtualisation, on trouve de plus en plus d&#8217;op\u00e9rations de red\u00e9marrages plus agressifs que les op\u00e9rations de maintenances plus classiques. En effet, il y a parfois des op\u00e9rations de bascules de VM entre h\u00f4tes, de la maintenance sur des&hellip; Continuer la lecture &rarr;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2022-11-14T14:16:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-19T10:28:37+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/reboot-lk.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"945\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Capdata team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Capdata team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 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\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/\"},\"author\":{\"name\":\"Capdata team\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/bfd9395c8ba4fa125792a543377035e9\"},\"headline\":\"Red\u00e9marrage des serveurs par l&#8217;hyperviseur : \u00e7a fait mal ?\",\"datePublished\":\"2022-11-14T14:16:24+00:00\",\"dateModified\":\"2023-01-19T10:28:37+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/\"},\"wordCount\":953,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"keywords\":[\"Accelerated Database Recovery\",\"ADR\",\"crash\",\"reboot\",\"recovery\",\"red\u00e9marrage\",\"restart\"],\"articleSection\":[\"SQL Server\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/\",\"name\":\"Red\u00e9marrage des serveurs par l'hyperviseur : \u00e7a fait mal ? - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2022-11-14T14:16:24+00:00\",\"dateModified\":\"2023-01-19T10:28:37+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Red\u00e9marrage des serveurs par l&#8217;hyperviseur : \u00e7a fait mal ?\"}]},{\"@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\/bfd9395c8ba4fa125792a543377035e9\",\"name\":\"Capdata team\",\"sameAs\":[\"https:\/\/www.capdata.fr\"],\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Red\u00e9marrage des serveurs par l'hyperviseur : \u00e7a fait mal ? - 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\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/","og_locale":"fr_FR","og_type":"article","og_title":"Red\u00e9marrage des serveurs par l'hyperviseur : \u00e7a fait mal ? - Capdata TECH BLOG","og_description":"Avec la virtualisation, on trouve de plus en plus d&#8217;op\u00e9rations de red\u00e9marrages plus agressifs que les op\u00e9rations de maintenances plus classiques. En effet, il y a parfois des op\u00e9rations de bascules de VM entre h\u00f4tes, de la maintenance sur des&hellip; Continuer la lecture &rarr;","og_url":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2022-11-14T14:16:24+00:00","article_modified_time":"2023-01-19T10:28:37+00:00","og_image":[{"width":945,"height":630,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/11\/reboot-lk.jpg","type":"image\/jpeg"}],"author":"Capdata team","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Capdata team","Dur\u00e9e de lecture estim\u00e9e":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/"},"author":{"name":"Capdata team","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/bfd9395c8ba4fa125792a543377035e9"},"headline":"Red\u00e9marrage des serveurs par l&#8217;hyperviseur : \u00e7a fait mal ?","datePublished":"2022-11-14T14:16:24+00:00","dateModified":"2023-01-19T10:28:37+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/"},"wordCount":953,"commentCount":0,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"keywords":["Accelerated Database Recovery","ADR","crash","reboot","recovery","red\u00e9marrage","restart"],"articleSection":["SQL Server"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/","url":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/","name":"Red\u00e9marrage des serveurs par l'hyperviseur : \u00e7a fait mal ? - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2022-11-14T14:16:24+00:00","dateModified":"2023-01-19T10:28:37+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/redemarrage-des-serveurs-par-lhyperviseur-ca-fait-mal\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"Red\u00e9marrage des serveurs par l&#8217;hyperviseur : \u00e7a fait mal ?"}]},{"@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\/bfd9395c8ba4fa125792a543377035e9","name":"Capdata team","sameAs":["https:\/\/www.capdata.fr"],"url":"https:\/\/blog.capdata.fr\/index.php\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/9481","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\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=9481"}],"version-history":[{"count":7,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/9481\/revisions"}],"predecessor-version":[{"id":9491,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/9481\/revisions\/9491"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/9492"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=9481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=9481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=9481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}