[{"data":1,"prerenderedAt":1149},["ShallowReactive",2],{"blog-\u002Fblog\u002Fles-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux":3,"blog-\u002Fblog\u002Fles-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux-surround":869,"blog-\u002Fblog\u002Fles-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux-certifications":928},{"id":4,"title":5,"body":6,"categories":853,"cover":855,"cover_contain":564,"credly_badge_id":856,"date":857,"description":858,"extension":859,"meta":860,"navigation":564,"path":861,"related_certifications":862,"seo":865,"slug":866,"stem":867,"__hash__":868},"blog\u002Fblog\u002Fles-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux.md","Les sauvegardes de mes machines KVM\u002FQEMU avec Veeam for Linux",{"type":7,"value":8,"toc":843},"minimark",[9,14,18,22,25,50,65,70,85,88,109,121,127,144,147,150,161,164,170,179,184,206,210,213,281,290,305,334,337,351,354,648,651,700,703,733,736,789,792,801,804,810,830,833,836,839],[10,11,13],"h2",{"id":12},"cas-dusage-concret","Cas d'usage concret",[15,16,17],"p",{},"Vous devez sauvegarder un parc de VM KVM\u002FQEMU de façon fiable : voici comment Veeam for Linux protège mon infrastructure.",[10,19,21],{"id":20},"les-sauvegardes-de-mes-machines-kvmqemu","Les sauvegardes de mes machines KVM\u002FQEMU",[15,23,24],{},"Depuis de nombreuses années, l’ensemble de mes services reposent sur des systèmes Linux. Ils me sont devenus indispensables au quotidien, notamment pour la gestion de mes données personnelles et plus généralement dans mes activités d’administrateur. J’ai souhaité donc pouvoir reprendre mon activité en cas de problème : instabilité logiciel, cyberattaque ou simplement en cas d’erreur humaine de ma part. J’ai donc entrepris de revoir mon plan de sauvegarde qui respecte alors la règle des 1-2-3 :",[26,27,28,37,44],"ul",{},[29,30,31,32,36],"li",{},"Disposer de ",[33,34,35],"strong",{},"trois copies de vos données"," au moins.",[29,38,39,40,43],{},"Stocker ces copies sur ",[33,41,42],{},"deux supports différents",".",[29,45,46,47,43],{},"Conserver ",[33,48,49],{},"une copie de la sauvegarde hors site",[15,51,52,53,62,64],{},"Dans mon plan, j’ai sélectionné la solution Veeam for Linux qui est gratuite est ",[54,55,59],"a",{"href":56,"rel":57},"https:\u002F\u002Fwww.veeam.com\u002Ffr\u002Flinux-backup-free.html",[58],"nofollow",[33,60,61],{},"disponible sur ce lien",[33,63,43],{}," Pour continuer à explorer les possibilités de la solution, j’utilise également Veeam Backup & Réplication v9.5 U2 qui est la console de management de Veeam (payant) que je n’évoquerai pas dans cet article.",[66,67,69],"h3",{"id":68},"le-sommaire","Le sommaire",[71,72,73,76,79,82],"ol",{},[29,74,75],{},"Le plan de désastre sur l’hôte KVM\u002FQEMU",[29,77,78],{},"Les sauvegardes des VM : mode image",[29,80,81],{},"L’installation de Veeam for Linux sur Debian 8",[29,83,84],{},"Conclusion sur mon plan de sauvegarde",[10,86,75],{"id":87},"le-plan-de-désastre-sur-lhôte-kvmqemu",[15,89,90,91,96,99,100,105,106,108],{},"La pièce maîtresse est mon hypeviseur KVM\u002FQEMU installé sur un ",[54,92,95],{"href":93,"rel":94},"https:\u002F\u002Fdocumentation.online.net\u002Ffr\u002Fdedicated-server\u002Foffers\u002Flimited\u002Fserver-dedibox-ent-deals-1701-6",[58],"serveur dédié HP DL160G8.",[97,98],"br",{},"\nEn cas de problème il doit être capable d’être restauré rapidement via ",[54,101,104],{"href":102,"rel":103},"https:\u002F\u002Fdocumentation.online.net\u002Ffr\u002Fdedicated-server\u002Fhardware\u002Fconfigure-ipmi-server\u002Fhp-ilo-controller",[58],"ILO."," J’ai décidé de réaliser une sauvegarde de l’ensemble de mes partitions (hormis \u002Fvar\u002Flibvirt\u002Flibvirt\u002Fimages qui contient les VM).",[97,107],{},"\nVoici mes différents emplacements de sauvegarde :",[15,110,111,112,114,115,117,118,120],{},"Emplacement 1Emplacement 2Emplacement 3 Un répertoire distant :",[97,113],{},"\nvia NFS avec ACLUn répertoire distant :",[97,116],{},"\nvia FTP avec ACLUn support chiffré",[97,119],{},"\nqui se trouve chez moi",[15,122,123],{},[124,125,126],"em",{},"Exemple : mon serveur est défectueux ou hors d’état de fonctionnement :",[71,128,129,134,139],{},[29,130,131],{},[124,132,133],{},"Lancement de la console Online.net pour activation de l’ILO.",[29,135,136],{},[124,137,138],{},"Démarrage du serveur depuis l’ISO Veeam Recovery Media.",[29,140,141],{},[124,142,143],{},"Récupération de mes volumes via mon repository accessible en NFS.",[10,145,78],{"id":146},"les-sauvegardes-des-vm-mode-image",[15,148,149],{},"Depuis de longues années, la virtualisation permet de créer des snapshots qui permettent à un instant T de figer l’état de la machine pour en déplacer et extraire toutes modifications vers un second emplacement temporaire. L’API libvirt me permet de réaliser aisément ses étapes de sauvegarde avec un script maison mais j’ai décidé de réaliser des sauvegardes en mode image du système Linux dans son intégralité avec l’agent Veeam for Linux. Comment cela fonctionne ?",[71,151,152,155,158],{},[29,153,154],{},"L’agent est installé sur l’ensemble des machines virtuelles.",[29,156,157],{},"La sauvegarde est paramétrée pour sauvegarder l’ensemble de la VM (mode image).",[29,159,160],{},"La sauvegarde est réalisée vers la destination : Veeam Backup & Réplication hébergé sur une VM Windows Server.",[15,162,163],{},"Emplacement 1Emplacement 2Emplacement 3",[15,165,166,167,169],{},"Une VM locale :",[97,168],{},"\nvers le disque V: Windows",[15,171,172,173,175,176,178],{},"Un répertoire distant :",[97,174],{},"\nvia FTPUn support chiffré",[97,177],{},"\nqui se trouve chez moi.",[15,180,181],{},[124,182,183],{},"Exemple : une VM est défectueuse ou hors d’état de fonctionnement :",[71,185,186,191,196,201],{},[29,187,188],{},[124,189,190],{},"Redémarrage forcé de la machine virtuelle.",[29,192,193],{},[124,194,195],{},"Récupération de mes volumes via l’application Veeam Backup & Réplication.",[29,197,198],{},[124,199,200],{},"Ou bien démarrage depuis l’ISO Veeam Recovery Media.",[29,202,203],{},[124,204,205],{},"Récupération de mes volumes via le repository Windows.",[10,207,209],{"id":208},"linstallation-de-veeam-for-linux-sur-debian-8","L’installation de Veeam for Linux sur Debian 8.",[15,211,212],{},"L’installation est très simple, quand bien même elle requiert 1GB de mémoire et certaines dépendances que voici :",[214,215,220],"pre",{"className":216,"code":217,"language":218,"meta":219,"style":219},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","apt-get install install dkms gcc make perl libudev-dev libacl1 libattr1-dev lvm2 libfuse-dev linux-headers-$(uname -r)\n","bash","",[221,222,223],"code",{"__ignoreMap":219},[224,225,228,232,236,238,241,244,247,250,253,256,259,262,265,268,272,275,278],"span",{"class":226,"line":227},"line",1,[224,229,231],{"class":230},"sBMFI","apt-get",[224,233,235],{"class":234},"sfazB"," install",[224,237,235],{"class":234},[224,239,240],{"class":234}," dkms",[224,242,243],{"class":234}," gcc",[224,245,246],{"class":234}," make",[224,248,249],{"class":234}," perl",[224,251,252],{"class":234}," libudev-dev",[224,254,255],{"class":234}," libacl1",[224,257,258],{"class":234}," libattr1-dev",[224,260,261],{"class":234}," lvm2",[224,263,264],{"class":234}," libfuse-dev",[224,266,267],{"class":234}," linux-headers-",[224,269,271],{"class":270},"sMK4o","$(",[224,273,274],{"class":230},"uname",[224,276,277],{"class":234}," -r",[224,279,280],{"class":270},")\n",[15,282,283,284,289],{},"Les ports utilisés par Veeam sont documentés sur la ",[54,285,288],{"href":286,"rel":287},"https:\u002F\u002Fhelpcenter.veeam.com\u002Fdocs\u002Fagentforlinux\u002Fuserguide\u002Fused_ports.html?ver=10",[58],"page du helpcenter",". Dans mon cas, la communication entre mon hôte KVM et le serveur NFS m’impose l’ouverture du port 2051. Pour les VM, elles devront communiquer avec le serveur veeam via le port : 10002 et la de 2500 à 5000 pour réaliser les sauvegardes.",[15,291,292,293,300,302,304],{},"Le téléchargement de Veeam software repository est disponible à ce ",[54,294,297],{"href":295,"rel":296},"https:\u002F\u002Fwww.veeam.com\u002Fdownloads.html",[58],[33,298,299],{},"lien",[33,301,43],{},[97,303],{},"\nLancer l’installation du paquage et exécuter une mise à jour des repository :",[214,306,308],{"className":216,"code":307,"language":218,"meta":219,"style":219},"dpkg -i .\u002Fveeam-release* && apt-get update\n",[221,309,310],{"__ignoreMap":219},[224,311,312,315,318,321,325,328,331],{"class":226,"line":227},[224,313,314],{"class":230},"dpkg",[224,316,317],{"class":234}," -i",[224,319,320],{"class":234}," .\u002Fveeam-release",[224,322,324],{"class":323},"sTEyZ","*",[224,326,327],{"class":270}," &&",[224,329,330],{"class":230}," apt-get",[224,332,333],{"class":234}," update\n",[15,335,336],{},"L’installation de Veeam est désormais disponible :",[214,338,340],{"className":216,"code":339,"language":218,"meta":219,"style":219},"apt-get install veeeam\n",[221,341,342],{"__ignoreMap":219},[224,343,344,346,348],{"class":226,"line":227},[224,345,231],{"class":230},[224,347,235],{"class":234},[224,349,350],{"class":234}," veeeam\n",[15,352,353],{},"Le résultat devrait être similaire à celui-ci :",[214,355,359],{"className":356,"code":357,"language":358,"meta":219,"style":219},"language-yaml shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","Lecture des listes de paquets... Fait\nConstruction de l'arbre des dépendances       \nLecture des informations d'état... Fait\nLes paquets supplémentaires suivants seront installés :\n  veeamsnap\nLes NOUVEAUX paquets suivants seront installés :\n  veeam veeamsnap\n0 mis à jour, 2 nouvellement installés, 0 à enlever et 1 non mis à jour.\nIl est nécessaire de prendre 22,8 Mo dans les archives.\nAprès cette opération, 51,8 Mo d'espace disque supplémentaires seront utilisés.\nSouhaitez-vous continuer ? [O\u002Fn] O\nRéception de : 1 http:\u002F\u002Frepository.veeam.com\u002Fbackup\u002Flinux\u002Fagent\u002Fdpkg\u002Fdebian\u002Fx86_64\u002F noname\u002Fveeam veeamsnap all 1.0.0.944 [71,1 kB]\nRéception de : 2 http:\u002F\u002Frepository.veeam.com\u002Fbackup\u002Flinux\u002Fagent\u002Fdpkg\u002Fdebian\u002Fx86_64\u002F noname\u002Fveeam veeam amd64 1.0.0.944 [22,8 MB]\n22,8 Mo réceptionnés en 1s (20,5 Mo\u002Fs)\nSélection du paquet veeamsnap précédemment désélectionné.\n(Lecture de la base de données... 58604 fichiers et répertoires déjà installés.)\nPréparation du dépaquetage de ...\u002Fveeamsnap_1.0.0.944_all.deb ...\nDépaquetage de veeamsnap (1.0.0.944) ...\nSélection du paquet veeam précédemment désélectionné.\nPréparation du dépaquetage de ...\u002Fveeam_1.0.0.944_amd64.deb ...\nDépaquetage de veeam (1.0.0.944) ...\nTraitement des actions différées (« triggers ») pour man-db (2.7.0.2-5) ...\nTraitement des actions différées (« triggers ») pour systemd (215-xxxxxx+xxxx) ...\nParamétrage de veeamsnap (1.0.0.944) ...\nLoading new veeamsnap-1.0.0.944 DKMS files...\nFirst Installation: checking all kernels...\nBuilding only for 3.xx.xx-x-amd64\nBuilding initial module for 3.xx.xx-x-amd64\nDone.\n\nveeamsnap:\nRunning module version sanity check.\n - Original module\n   - No original module exists within this kernel\n - Installation\n   - Installing to \u002Flib\u002Fmodules\u002F3.xx.xx-x-amd64\u002Fupdates\u002Fdkms\u002F\n\ndepmod............\n\nDKMS: install completed.\nParamétrage de veeam (1.0.0.944) ...\n","yaml",[221,360,361,366,375,381,391,397,405,411,417,423,429,435,447,457,463,469,475,481,487,493,499,505,511,517,523,529,541,547,553,559,566,575,581,590,599,607,615,620,626,631,642],{"__ignoreMap":219},[224,362,363],{"class":226,"line":227},[224,364,365],{"class":234},"Lecture des listes de paquets... Fait\n",[224,367,369,372],{"class":226,"line":368},2,[224,370,371],{"class":234},"Construction de l'arbre des dépendances",[224,373,374],{"class":323},"       \n",[224,376,378],{"class":226,"line":377},3,[224,379,380],{"class":234},"Lecture des informations d'état... Fait\n",[224,382,384,388],{"class":226,"line":383},4,[224,385,387],{"class":386},"swJcz","Les paquets supplémentaires suivants seront installés",[224,389,390],{"class":270}," :\n",[224,392,394],{"class":226,"line":393},5,[224,395,396],{"class":234},"  veeamsnap\n",[224,398,400,403],{"class":226,"line":399},6,[224,401,402],{"class":386},"Les NOUVEAUX paquets suivants seront installés",[224,404,390],{"class":270},[224,406,408],{"class":226,"line":407},7,[224,409,410],{"class":234},"  veeam veeamsnap\n",[224,412,414],{"class":226,"line":413},8,[224,415,416],{"class":234},"0 mis à jour, 2 nouvellement installés, 0 à enlever et 1 non mis à jour.\n",[224,418,420],{"class":226,"line":419},9,[224,421,422],{"class":234},"Il est nécessaire de prendre 22,8 Mo dans les archives.\n",[224,424,426],{"class":226,"line":425},10,[224,427,428],{"class":234},"Après cette opération, 51,8 Mo d'espace disque supplémentaires seront utilisés.\n",[224,430,432],{"class":226,"line":431},11,[224,433,434],{"class":234},"Souhaitez-vous continuer ? [O\u002Fn] O\n",[224,436,438,441,444],{"class":226,"line":437},12,[224,439,440],{"class":386},"Réception de",[224,442,443],{"class":270}," :",[224,445,446],{"class":234}," 1 http:\u002F\u002Frepository.veeam.com\u002Fbackup\u002Flinux\u002Fagent\u002Fdpkg\u002Fdebian\u002Fx86_64\u002F noname\u002Fveeam veeamsnap all 1.0.0.944 [71,1 kB]\n",[224,448,450,452,454],{"class":226,"line":449},13,[224,451,440],{"class":386},[224,453,443],{"class":270},[224,455,456],{"class":234}," 2 http:\u002F\u002Frepository.veeam.com\u002Fbackup\u002Flinux\u002Fagent\u002Fdpkg\u002Fdebian\u002Fx86_64\u002F noname\u002Fveeam veeam amd64 1.0.0.944 [22,8 MB]\n",[224,458,460],{"class":226,"line":459},14,[224,461,462],{"class":234},"22,8 Mo réceptionnés en 1s (20,5 Mo\u002Fs)\n",[224,464,466],{"class":226,"line":465},15,[224,467,468],{"class":234},"Sélection du paquet veeamsnap précédemment désélectionné.\n",[224,470,472],{"class":226,"line":471},16,[224,473,474],{"class":234},"(Lecture de la base de données... 58604 fichiers et répertoires déjà installés.)\n",[224,476,478],{"class":226,"line":477},17,[224,479,480],{"class":234},"Préparation du dépaquetage de ...\u002Fveeamsnap_1.0.0.944_all.deb ...\n",[224,482,484],{"class":226,"line":483},18,[224,485,486],{"class":234},"Dépaquetage de veeamsnap (1.0.0.944) ...\n",[224,488,490],{"class":226,"line":489},19,[224,491,492],{"class":234},"Sélection du paquet veeam précédemment désélectionné.\n",[224,494,496],{"class":226,"line":495},20,[224,497,498],{"class":234},"Préparation du dépaquetage de ...\u002Fveeam_1.0.0.944_amd64.deb ...\n",[224,500,502],{"class":226,"line":501},21,[224,503,504],{"class":234},"Dépaquetage de veeam (1.0.0.944) ...\n",[224,506,508],{"class":226,"line":507},22,[224,509,510],{"class":234},"Traitement des actions différées (« triggers ») pour man-db (2.7.0.2-5) ...\n",[224,512,514],{"class":226,"line":513},23,[224,515,516],{"class":234},"Traitement des actions différées (« triggers ») pour systemd (215-xxxxxx+xxxx) ...\n",[224,518,520],{"class":226,"line":519},24,[224,521,522],{"class":234},"Paramétrage de veeamsnap (1.0.0.944) ...\n",[224,524,526],{"class":226,"line":525},25,[224,527,528],{"class":234},"Loading new veeamsnap-1.0.0.944 DKMS files...\n",[224,530,532,535,538],{"class":226,"line":531},26,[224,533,534],{"class":386},"First Installation",[224,536,537],{"class":270},":",[224,539,540],{"class":234}," checking all kernels...\n",[224,542,544],{"class":226,"line":543},27,[224,545,546],{"class":234},"Building only for 3.xx.xx-x-amd64\n",[224,548,550],{"class":226,"line":549},28,[224,551,552],{"class":234},"Building initial module for 3.xx.xx-x-amd64\n",[224,554,556],{"class":226,"line":555},29,[224,557,558],{"class":234},"Done.\n",[224,560,562],{"class":226,"line":561},30,[224,563,565],{"emptyLinePlaceholder":564},true,"\n",[224,567,569,572],{"class":226,"line":568},31,[224,570,571],{"class":386},"veeamsnap",[224,573,574],{"class":270},":\n",[224,576,578],{"class":226,"line":577},32,[224,579,580],{"class":234},"Running module version sanity check.\n",[224,582,584,587],{"class":226,"line":583},33,[224,585,586],{"class":270}," -",[224,588,589],{"class":234}," Original module\n",[224,591,593,596],{"class":226,"line":592},34,[224,594,595],{"class":270},"   -",[224,597,598],{"class":234}," No original module exists within this kernel\n",[224,600,602,604],{"class":226,"line":601},35,[224,603,586],{"class":270},[224,605,606],{"class":234}," Installation\n",[224,608,610,612],{"class":226,"line":609},36,[224,611,595],{"class":270},[224,613,614],{"class":234}," Installing to \u002Flib\u002Fmodules\u002F3.xx.xx-x-amd64\u002Fupdates\u002Fdkms\u002F\n",[224,616,618],{"class":226,"line":617},37,[224,619,565],{"emptyLinePlaceholder":564},[224,621,623],{"class":226,"line":622},38,[224,624,625],{"class":234},"depmod............\n",[224,627,629],{"class":226,"line":628},39,[224,630,565],{"emptyLinePlaceholder":564},[224,632,634,637,639],{"class":226,"line":633},40,[224,635,636],{"class":386},"DKMS",[224,638,537],{"class":270},[224,640,641],{"class":234}," install completed.\n",[224,643,645],{"class":226,"line":644},41,[224,646,647],{"class":234},"Paramétrage de veeam (1.0.0.944) ...\n",[15,649,650],{},"J’ai rencontré un soucis sur une VM lors du lancement du module veeamsnap,  un code d’erreur apparaît :",[214,652,654],{"className":216,"code":653,"language":218,"meta":219,"style":219},"Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].\n",[221,655,656],{"__ignoreMap":219},[224,657,658,661,664,667,670,673,676,679,682,686,689,691,694,697],{"class":226,"line":227},[224,659,660],{"class":230},"Failed",[224,662,663],{"class":234}," to",[224,665,666],{"class":234}," load",[224,668,669],{"class":234}," module",[224,671,672],{"class":323}," [veeamsnap] with parameters ",[224,674,675],{"class":270},"[",[224,677,678],{"class":323},"zerosnapdata",[224,680,681],{"class":270},"=",[224,683,685],{"class":684},"sbssI","1",[224,687,688],{"class":323}," debuglogging",[224,690,681],{"class":270},[224,692,693],{"class":323},"0",[224,695,696],{"class":270},"]",[224,698,699],{"class":323},".\n",[15,701,702],{},"Pour résoudre le problème, voici la marche à suivre :",[214,704,706],{"className":216,"code":705,"language":218,"meta":219,"style":219},"dkms status\nveeamsnap, 1.0.0.944, 3.xx.xx-x-amd64, x86_64: installed\n",[221,707,708,716],{"__ignoreMap":219},[224,709,710,713],{"class":226,"line":227},[224,711,712],{"class":230},"dkms",[224,714,715],{"class":234}," status\n",[224,717,718,721,724,727,730],{"class":226,"line":368},[224,719,720],{"class":230},"veeamsnap,",[224,722,723],{"class":234}," 1.0.0.944,",[224,725,726],{"class":234}," 3.xx.xx-x-amd64,",[224,728,729],{"class":234}," x86_64:",[224,731,732],{"class":234}," installed\n",[15,734,735],{},"Il faut le supprimer, le rebuilt et le réinstaller pour qu’il se charge ensuite normalement :",[214,737,739],{"className":216,"code":738,"language":218,"meta":219,"style":219},"dkms remove -m veeamsnap\u002F1.0.0.944 --all\ndkms build -m veeamsnap -v 1.0.0.944\ndkms install -m veeamsnap -v 1.0.0.944\n",[221,740,741,757,775],{"__ignoreMap":219},[224,742,743,745,748,751,754],{"class":226,"line":227},[224,744,712],{"class":230},[224,746,747],{"class":234}," remove",[224,749,750],{"class":234}," -m",[224,752,753],{"class":234}," veeamsnap\u002F1.0.0.944",[224,755,756],{"class":234}," --all\n",[224,758,759,761,764,766,769,772],{"class":226,"line":368},[224,760,712],{"class":230},[224,762,763],{"class":234}," build",[224,765,750],{"class":234},[224,767,768],{"class":234}," veeamsnap",[224,770,771],{"class":234}," -v",[224,773,774],{"class":684}," 1.0.0.944\n",[224,776,777,779,781,783,785,787],{"class":226,"line":377},[224,778,712],{"class":230},[224,780,235],{"class":234},[224,782,750],{"class":234},[224,784,768],{"class":234},[224,786,771],{"class":234},[224,788,774],{"class":684},[15,790,791],{},"L’installation de Veeam for Linux sous Debian 8 est terminée. Désormais la commande principale de création de job est :",[214,793,795],{"className":216,"code":794,"language":218,"meta":219,"style":219},"veeam\n",[221,796,797],{"__ignoreMap":219},[224,798,799],{"class":226,"line":227},[224,800,794],{"class":230},[15,802,803],{},"Veeam Agent for Linux apparaît dans le terminal, il nous propose d’utiliser le produit gratuitement ou avec une licence :",[15,805,806],{},[807,808],"img",{"alt":219,"src":809},"\u002Fimages\u002Fblog\u002Fles-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux\u002F8b3111fce8.png",[15,811,812,813,815,816,821,822,828],{},"Désormais, vous êtes fin prêt à réaliser vous aussi votre plan de sauvegarde avec la solution Veeam For Linux.",[97,814],{},"\nPour les instructions en ligne de commande : création de job, suppression, etc… ",[54,817,820],{"href":818,"rel":819},"https:\u002F\u002Fhelpcenter.veeam.com\u002Fdocs\u002Fagentforlinux\u002Fuserguide\u002Fbackup_job_create_cmd.html?ver=10",[58],"c’est"," ",[54,823,825],{"href":818,"rel":824},[58],[33,826,827],{},"par ici",[33,829,43],{},[10,831,84],{"id":832},"conclusion-sur-mon-plan-de-sauvegarde",[15,834,835],{},"Je crois que le plus long n’est pas de sélectionner la solution de sauvegarde mais bien de réfléchir au plan de sauvegarde en lui-même. Au cas échéant, celui-ci orientera forcement le choix de la solution de sauvegarde.",[15,837,838],{},"J’ajouterai également qu’une semaine après mon plan de sauvegarde déployé je me suis décidé à faire un test de restauration de l’ensemble de mes machines.  Pour conclure, le plan de reprise d’activité fonctionne parfaitement et ma rétention est de 15 jours. Veeam for Linux est une solution que je vous conseille d’autant qu’elle est gratuite.",[840,841,842],"style",{},"html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html pre.shiki code .sMK4o, html code.shiki .sMK4o{--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sTEyZ, html code.shiki .sTEyZ{--shiki-light:#90A4AE;--shiki-default:#EEFFFF;--shiki-dark:#BABED8}html pre.shiki code .swJcz, html code.shiki .swJcz{--shiki-light:#E53935;--shiki-default:#F07178;--shiki-dark:#F07178}html pre.shiki code .sbssI, html code.shiki .sbssI{--shiki-light:#F76D47;--shiki-default:#F78C6C;--shiki-dark:#F78C6C}",{"title":219,"searchDepth":368,"depth":368,"links":844},[845,846,849,850,851,852],{"id":12,"depth":368,"text":13},{"id":20,"depth":368,"text":21,"children":847},[848],{"id":68,"depth":377,"text":69},{"id":87,"depth":368,"text":75},{"id":146,"depth":368,"text":78},{"id":208,"depth":368,"text":209},{"id":832,"depth":368,"text":84},[854],"Linux","\u002Fimages\u002Fblog\u002Fles-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux\u002Fdb83b58b53.png",null,"2017-07-09","Découvrez comment Veeam pour Linux sauvegarde mon infrastructure KVM\u002FQEMU.","md",{},"\u002Fblog\u002Fles-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux",[863,864],"certificat-veeam-certified-engineer-vmce","certificat-lpi-linux-essentials-exam-010-150",{"title":5,"description":858},"les-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux","blog\u002Fles-sauvegardes-mes-machines-kvm-qemu-avec-veeam-for-linux","D5F-rRqVGpdGtTpncr5wxC52yuF7Dsl6-eXijTdxg2U",[870,878,885,892,900,908,914,921],{"title":871,"path":872,"stem":873,"date":874,"cover":875,"categories":876,"children":-1},"Veeam Backup et Replication sous Windows Server 2016 Core","\u002Fblog\u002Fveeam-backup-replication-sous-windows-server-2016-core","blog\u002Fveeam-backup-replication-sous-windows-server-2016-core","2017-10-29","\u002Fimages\u002Fblog\u002Fveeam-backup-replication-sous-windows-server-2016-core\u002Fb6d80a8d4b.jpg",[877],"Microsoft",{"title":879,"path":880,"stem":881,"date":882,"cover":883,"categories":884,"children":-1},"Intégration de Windows Server 2016 core sous KVM\u002FQEMU","\u002Fblog\u002Fintegration-windows-server-2016-core-sous-kvm-qemu","blog\u002Fintegration-windows-server-2016-core-sous-kvm-qemu","2017-10-17","\u002Fimages\u002Fblog\u002Fintegration-windows-server-2016-core-sous-kvm-qemu\u002F9b895102f9.jpg",[854],{"title":886,"path":887,"stem":888,"date":889,"cover":890,"categories":891,"children":-1},"Installation et configuration de Zextras Suite","\u002Fblog\u002Finstallation-configuration-zextras-suite","blog\u002Finstallation-configuration-zextras-suite","2017-10-07","\u002Fimages\u002Fblog\u002Finstallation-configuration-zextras-suite\u002F3cc0db9e57.png",[854],{"title":893,"path":894,"stem":895,"date":896,"cover":897,"categories":898,"children":-1},"Une nuit à l’éco-site Oasis Bellecombe","\u002Fblog\u002Fune-nuit-eco-site-oasis-bellecombe","blog\u002Fune-nuit-eco-site-oasis-bellecombe","2017-09-09","\u002Fimages\u002Fblog\u002Fune-nuit-eco-site-oasis-bellecombe\u002Ff6ac468e74.jpg",[899],"Évènement",{"title":901,"path":902,"stem":903,"date":904,"cover":905,"categories":906,"children":-1},"ESET Remote Administrator : prise en main de la web console","\u002Fblog\u002Feset-remote-administrator-prise-main-web-console","blog\u002Feset-remote-administrator-prise-main-web-console","2017-05-30","\u002Fimages\u002Fblog\u002Feset-remote-administrator-prise-main-web-console\u002F15dab17188.jpg",[907],"Sécurité",{"title":909,"path":910,"stem":911,"date":912,"cover":913,"categories":856,"children":-1},"Mise à jour du routeur SRX 100 sous Junos","\u002Fblog\u002Fmise-jour-routeur-srx-100-sous-junos","blog\u002Fmise-jour-routeur-srx-100-sous-junos","2017-05-17","\u002Fimages\u002Fblog\u002Fmise-jour-routeur-srx-100-sous-junos\u002F1b4814003c.jpg",{"title":915,"path":916,"stem":917,"date":918,"cover":919,"categories":920,"children":-1},"ESET Remote Administrator : installation sous Windows","\u002Fblog\u002Feset-remote-administrator-installation-sous-windows","blog\u002Feset-remote-administrator-installation-sous-windows","2017-04-30","\u002Fimages\u002Fblog\u002Feset-remote-administrator-installation-sous-windows\u002F15dab17188.jpg",[877],{"title":922,"path":923,"stem":924,"date":925,"cover":926,"categories":927,"children":-1},"Hack In Paris et Nuit du Hack du 19 au 25 Juin 2017","\u002Fblog\u002Fhack-paris-nuit-hack-juin-2017","blog\u002Fhack-paris-nuit-hack-juin-2017","2017-04-25","\u002Fimages\u002Fblog\u002Fhack-paris-nuit-hack-juin-2017\u002F4cd713ef6f.png",[899],[929,1080],{"id":930,"title":931,"body":932,"categories":1069,"cover":1071,"cover_contain":564,"credly_badge_id":1072,"date":1073,"description":1074,"extension":859,"meta":1075,"navigation":564,"path":1076,"related_certifications":856,"seo":1077,"slug":863,"stem":1078,"__hash__":1079},"blog\u002Fblog\u002Fcertificat-veeam-certified-engineer-vmce.md","Veeam Certified Engineer (VMCE)",{"type":7,"value":933,"toc":1065},[934,936,939,945,1052,1058,1062],[10,935,13],{"id":12},[15,937,938],{},"Pour concevoir et dépanner des plans de sauvegarde Veeam fiables chez mes clients, j'ai passé cette certification VMCE.",[15,940,941,942,944],{},"Le parcours de formation \"Veeam Certified Engineer\" est dédié aux professionnels IT responsable de Veeam Backup & Replication.",[97,943],{},"\nLe catalogue de cours aborde les modules suivants :",[26,946,947,952,957,962,967,972,977,982,987,992,997,1002,1007,1012,1017,1022,1027,1032,1037,1042,1047],{},[29,948,949],{},[33,950,951],{},"Data protection strategies",[29,953,954],{},[33,955,956],{},"Risk scenarios",[29,958,959],{},[33,960,961],{},"Core components",[29,963,964],{},[33,965,966],{},"Initial security considerations",[29,968,969],{},[33,970,971],{},"Virtual machine backup",[29,973,974],{},[33,975,976],{},"Agent backup",[29,978,979],{},[33,980,981],{},"Unstructured data backup",[29,983,984],{},[33,985,986],{},"Backup data optimizations",[29,988,989],{},[33,990,991],{},"Immutability and hardened repositories",[29,993,994],{},[33,995,996],{},"Object storage",[29,998,999],{},[33,1000,1001],{},"Transport modes",[29,1003,1004],{},[33,1005,1006],{},"Backup copies",[29,1008,1009],{},[33,1010,1011],{},"Scale-out Backup Repository",[29,1013,1014],{},[33,1015,1016],{},"Moving or copying backups",[29,1018,1019],{},[33,1020,1021],{},"Replication",[29,1023,1024],{},[33,1025,1026],{},"Verifying recoverability",[29,1028,1029],{},[33,1030,1031],{},"Veeam Backup Enterprise Manager",[29,1033,1034],{},[33,1035,1036],{},"Incident Response Planning",[29,1038,1039],{},[33,1040,1041],{},"Recovery scenarios and features",[29,1043,1044],{},[33,1045,1046],{},"Enacting a recovery",[29,1048,1049],{},[33,1050,1051],{},"Veeam Data Platform",[15,1053,1054,1055,1057],{},"le temps à accorder à la formation est d'environ 4 jours.",[97,1056],{},"\nIl faut ensuite prévoir environ 1h45 pour le passage de la certification : Veeam Certified Engineer.",[10,1059,1061],{"id":1060},"conclusion","Conclusion",[15,1063,1064],{},"La certification Veeam Certified Engineer valide une expertise complète sur Veeam Backup & Replication : stratégies de protection des données, sauvegarde des VM et des agents, optimisation, immuabilité et réplication. Avec environ 4 jours de formation et 1h45 d'examen, elle couvre aussi bien la mise en œuvre que la gestion des scénarios de restauration. C'est une certification clé pour toute personne responsable de la protection des données en environnement virtualisé.",{"title":219,"searchDepth":368,"depth":368,"links":1066},[1067,1068],{"id":12,"depth":368,"text":13},{"id":1060,"depth":368,"text":1061},[1070],"Certifications","\u002Fimages\u002Fblog\u002Fcertificat-veeam-certified-engineer-vmce\u002F4dd7c37e93.png","21923881-9ebd-4f03-9e06-0af121aea5cb","2024-08-24","Veeam Certified Engineer (VMCE) : formation Pearson VUE, suivie pour ma veille professionnelle en cybersécurité et informatique.",{},"\u002Fblog\u002Fcertificat-veeam-certified-engineer-vmce",{"title":931,"description":1074},"blog\u002Fcertificat-veeam-certified-engineer-vmce","6dYCxxK8lEm2JY3ZQiYm5QKBgndTuT_sXCDEIyMiMH0",{"id":1081,"title":1082,"body":1083,"categories":1138,"cover":1139,"cover_contain":1140,"credly_badge_id":1141,"date":1142,"description":1143,"extension":859,"meta":1144,"navigation":564,"path":1145,"related_certifications":856,"seo":1146,"slug":864,"stem":1147,"__hash__":1148},"blog\u002Fblog\u002Fcertificat-lpi-linux-essentials-exam-010-150.md","LPI Linux Essentials – Exam 010-150",{"type":7,"value":1084,"toc":1134},[1085,1087,1090,1096,1123,1129,1131],[10,1086,13],{"id":12},[15,1088,1089],{},"Pour fiabiliser mes interventions sur des serveurs Linux en clientèle, j'ai passé cette certification LPI Linux Essentials.",[15,1091,1092,1093,1095],{},"Le parcours de formation \"LPI Linux Essentials\" est dédié aux professionnels des systèmes.",[97,1094],{},"\nLe catalogue de cours en ligne aborde les modules suivants :",[26,1097,1098,1103,1108,1113,1118],{},[29,1099,1100],{},[33,1101,1102],{},"Communauté Linux et carrière dans le logiciel libre",[29,1104,1105],{},[33,1106,1107],{},"Trouver son chemin sur un système Linux",[29,1109,1110],{},[33,1111,1112],{},"Le pouvoir de la ligne de commande",[29,1114,1115],{},[33,1116,1117],{},"Le système d'exploitation Linux",[29,1119,1120],{},[33,1121,1122],{},"Sécurité et droits d'accès aux fichiers",[15,1124,1125,1126,1128],{},"le temps à accorder à la formation est d'environ 2 jours.",[97,1127],{},"\nIl faut ensuite prévoir environ 1h pour le passage de la certification : LPI Linux Essentials.",[10,1130,1061],{"id":1060},[15,1132,1133],{},"Cette formation via NDG prépare à la certification LPI Linux Essentials, en couvrant les bases de l'écosystème Linux : ligne de commande, système d'exploitation et sécurité des fichiers. Elle constitue une première certification solide pour toute personne débutant sur les systèmes Linux. Un socle indispensable avant d'aborder des certifications Linux plus avancées.",{"title":219,"searchDepth":368,"depth":368,"links":1135},[1136,1137],{"id":12,"depth":368,"text":13},{"id":1060,"depth":368,"text":1061},[1070,854],"\u002Fimages\u002Fblog\u002Fcertificat-lpi-linux-essentials-exam-010-150\u002F4497f02702.jpg",false,"dbc3a0e7-5909-47df-b9b1-c05ecb60ccb4","2017-11-24","Certification LPI Linux Essentials Exam 010-150 via un cours en ligne NDG.",{},"\u002Fblog\u002Fcertificat-lpi-linux-essentials-exam-010-150",{"title":1082,"description":1143},"blog\u002Fcertificat-lpi-linux-essentials-exam-010-150","dWE6IEkGgqM6lYMKZ-nr8Wu-9p_hkgSwca7ZOpKGQtQ",1786644874166]