{"id":803,"date":"2024-03-01T00:00:00","date_gmt":"2024-02-29T21:00:00","guid":{"rendered":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/?p=803"},"modified":"2026-10-06T02:41:35","modified_gmt":"2026-10-05T23:41:35","slug":"vmware-site-recovery-manager-nedir","status":"publish","type":"post","link":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/guvenlik\/vmware-site-recovery-manager-nedir\/","title":{"rendered":"VMWare Site Recovery Manager Nedir?"},"content":{"rendered":"
\n

Bu rehber, VMware Site Recovery Manager (SRM) i\u00e7in ara\u015ft\u0131rma yapan ekiplerin kurtarma plan\u0131 tasarlamas\u0131na odaklan\u0131r. Kaynak olarak verilen Protection and Recovery 9.1 belgesi; sanal makinelerin, a\u00e7\u0131l\u0131\u015f s\u0131ras\u0131n\u0131n ve a\u011f ayarlar\u0131n\u0131n bir kurtarma plan\u0131yla nas\u0131l d\u00fczenlendi\u011fini a\u00e7\u0131klar. \u0130\u015flem ad\u0131mlar\u0131n\u0131 kurulu \u00fcr\u00fcn ve s\u00fcr\u00fcmle e\u015fle\u015ftirin. Veri \u00e7o\u011faltma, yedek saklama ve uygulama do\u011frulamas\u0131 ayr\u0131 sorumluluklar olmaya devam eder.<\/p>\n

\"Korunan
Veri hareketi ile kurtarma ad\u0131mlar\u0131n\u0131n y\u00f6netimi ayr\u0131 katmanlard\u0131r.
G\u00f6rseli b\u00fcy\u00fct \u2192<\/a><\/figcaption><\/figure>\n

Orkestrasyon neyi y\u00f6netir?<\/h2>\n

Kurtarma yaln\u0131z sanal makineleri a\u00e7mak de\u011fildir. A\u011f e\u015fle\u015ftirmesi, IP ve DNS d\u00fczeni, uygulama ba\u011f\u0131ml\u0131l\u0131klar\u0131 ve a\u00e7\u0131l\u0131\u015f s\u0131ras\u0131 birlikte ele al\u0131n\u0131r. Bir veritaban\u0131 haz\u0131r olmadan uygulama sunucusunun a\u00e7\u0131lmas\u0131 kullan\u0131c\u0131n\u0131n hizmet alabildi\u011fini g\u00f6stermez. Plan, bu ba\u011f\u0131ml\u0131l\u0131klar\u0131 ve do\u011frulama ad\u0131mlar\u0131n\u0131 g\u00f6r\u00fcn\u00fcr hale getirmelidir.<\/p>\n

SRM ile ili\u015fkili veri \u00e7o\u011faltma se\u00e7enekleri kurulu s\u00fcr\u00fcm ve desteklenen altyap\u0131ya ba\u011fl\u0131d\u0131r. vSphere Replication veya desteklenen depolama entegrasyonlar\u0131 gibi yollar\u0131n ko\u015fullar\u0131 ayn\u0131 de\u011fildir. \u00dcr\u00fcn ailesinin g\u00fcncel ad\u0131n\u0131, uyumluluk matrisini ve lisans kapsam\u0131n\u0131 mevcut kurulumla e\u015fle\u015ftirmeden eski bir kurulum tarifini uygulamay\u0131n.<\/p>\n

Replikasyon, yedek ve kurtarma plan\u0131<\/h2>\n

Replikasyon, verinin ba\u015fka bir konuma aktar\u0131lmas\u0131n\u0131 sa\u011flar; hatal\u0131 silme veya bozulma da \u00e7o\u011falt\u0131labilir. Yedekleme, uygun saklama politikas\u0131yla ge\u00e7mi\u015f bir duruma d\u00f6nme ihtiyac\u0131na hizmet eder. Kurtarma orkestrasyonu ise se\u00e7ilen kopyayla hizmeti yeniden \u00e7al\u0131\u015ft\u0131racak ad\u0131mlar\u0131 d\u00fczenler. Bu \u00fc\u00e7 i\u015flev birbirinin b\u00fct\u00fcn g\u00f6revlerini \u00fcstlenmez.<\/p>\n

RPO, kabul edilebilir veri kayb\u0131 aral\u0131\u011f\u0131n\u0131; RTO, hizmete d\u00f6n\u00fc\u015f i\u00e7in hedeflenen s\u00fcreyi tan\u0131mlar. \u0130kisi de i\u015f ihtiyac\u0131ndan t\u00fcretilmelidir. Replikasyon aral\u0131\u011f\u0131 tek ba\u015f\u0131na uygulaman\u0131n ger\u00e7ek veri kayb\u0131n\u0131, sanal makinenin a\u00e7\u0131l\u0131\u015f s\u00fcresi de tam hizmete d\u00f6n\u00fc\u015f s\u00fcresini kesinle\u015ftirmez.<\/p>\n

Planl\u0131 ge\u00e7i\u015f ve kesinti sonras\u0131 kurtarma<\/h2>\n

Planl\u0131 ge\u00e7i\u015fte kaynak ortamla koordinasyon kurmak ve son veriyi e\u015fitlemek m\u00fcmk\u00fcn olabilir. Beklenmedik kesintide kaynak eri\u015filemeyebilir; son kullan\u0131labilir kopya ve mevcut altyap\u0131yla karar verilmesi gerekir. Bu iki senaryonun kontrol ve veri kayb\u0131 ko\u015fullar\u0131 ayn\u0131 de\u011fildir.<\/p>\n

Ayn\u0131 uygulaman\u0131n iki tarafta kontrols\u00fcz yazma yapmas\u0131 veri ayr\u0131\u015fmas\u0131na yol a\u00e7abilir. Kaynak taraf\u0131n durumunu, eri\u015fim kesme ad\u0131mlar\u0131n\u0131 ve yetkili karar sahibini planlay\u0131n. \u201cKurtar\u201d d\u00fc\u011fmesine bas\u0131lmas\u0131, kullan\u0131c\u0131 trafi\u011finin do\u011fru yere gitti\u011fini veya eski \u00f6rne\u011fin g\u00fcvenli \u015fekilde devreden \u00e7\u0131kt\u0131\u011f\u0131n\u0131 tek ba\u015f\u0131na g\u00f6stermez.<\/p>\n

Testte uygulamay\u0131 do\u011frulay\u0131n<\/h2>\n
    \n
  1. Deneme a\u011f\u0131n\u0131n \u00fcretim sistemlerine istenmeyen eri\u015fim veya bildirim \u00fcretmedi\u011fini kontrol edin.<\/li>\n
  2. Veritaban\u0131, kimlik, DNS, lisans ve d\u0131\u015f servis ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 hesaba kat\u0131n.<\/li>\n
  3. Temsil\u00ee kullan\u0131c\u0131 i\u015flemleriyle okuma ve yazma b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc do\u011frulay\u0131n.<\/li>\n
  4. Ger\u00e7ekle\u015fen s\u00fcreleri, kullan\u0131lan veri noktas\u0131n\u0131 ve ba\u015far\u0131s\u0131z ad\u0131mlar\u0131 kaydedin.<\/li>\n
  5. Test kaynaklar\u0131n\u0131 ve ge\u00e7ici eri\u015fimleri kontroll\u00fc \u015fekilde temizleyin.<\/li>\n<\/ol>\n

    Bir testin ge\u00e7mi\u015fte ba\u015far\u0131l\u0131 olmas\u0131 yeni s\u00fcr\u00fcm, a\u011f de\u011fi\u015fikli\u011fi veya farkl\u0131 veri boyutunda ayn\u0131 sonucu garanti etmez. Kurtarma plan\u0131n\u0131 \u00f6nemli de\u011fi\u015fikliklerden sonra yeniden de\u011ferlendirin. Deneme sonucunu \u201cmakineler a\u00e7\u0131ld\u0131\u201d yerine uygulama kabul \u00f6l\u00e7\u00fctleriyle raporlay\u0131n.<\/p>\n

    Geri d\u00f6n\u00fc\u015f\u00fc ba\u015ftan planlay\u0131n<\/h2>\n

    \u0130kincil ortamda \u00e7al\u0131\u015fmaya ba\u015flad\u0131ktan sonra kaynak sisteme d\u00f6nmek ayr\u0131 bir s\u00fcre\u00e7tir. Yeni verinin hangi y\u00f6nde korunaca\u011f\u0131, yeniden koruma i\u015flemleri ve bir sonraki ge\u00e7i\u015fin ko\u015fullar\u0131 belirlenmelidir. Desteklenen s\u00fcr\u00fcme g\u00f6re s\u00fcre\u00e7 de\u011fi\u015febilir. Geri d\u00f6n\u00fc\u015f plan\u0131 yoksa ge\u00e7ici kurtarma ortam\u0131 beklenenden uzun s\u00fcre tek \u00fcretim noktas\u0131 haline gelebilir.<\/p>\n

    S\u0131k sorulan sorular<\/h2>\n
    \n
    SRM yedekleme \u00fcr\u00fcn\u00fc m\u00fcd\u00fcr?<\/strong><\/dt>\n
    \n

    Temel rol\u00fc kurtarma ad\u0131mlar\u0131n\u0131 orkestre etmektir. Kullan\u0131lan veri kopyas\u0131, replikasyon ve ge\u00e7mi\u015f s\u00fcr\u00fcmlerden geri y\u00fckleme gereksinimi ayr\u0131ca tasarlan\u0131r.<\/p>\n<\/dd>\n

    Ba\u015far\u0131l\u0131 kurtarma testi kesinti olmayaca\u011f\u0131n\u0131 garanti eder mi?<\/strong><\/dt>\n
    \n

    Hay\u0131r. Test belirli ko\u015fullarda kan\u0131t sa\u011flar. Yeni ba\u011f\u0131ml\u0131l\u0131klar, veri b\u00fcy\u00fcmesi ve ger\u00e7ek ar\u0131zan\u0131n niteli\u011fi sonucu de\u011fi\u015ftirebilir.<\/p>\n<\/dd>\n<\/dl>\n

    Sonraki ad\u0131m<\/h2>\n

    Replikasyon<\/a> ve yedekleme<\/a> rehberlerini birlikte kullan\u0131n. \u00d6nce i\u015fin veri kayb\u0131 ve hizmete d\u00f6n\u00fc\u015f hedeflerini yaz\u0131n; ard\u0131ndan kurulu \u00fcr\u00fcne uygun kurtarma ak\u0131\u015f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n

    Kaynaklar<\/h2>\n
      \n
    1. Broadcom \u2014 Protection and Recovery 9.1: plans, testing and recovery modes<\/a><\/li>\n
    2. NIST SP 800-34 Rev. 1 \u2014 Contingency Planning Guide for Federal Information Systems<\/a><\/li>\n
    3. NIST SP 800-125 \u2014 Guide to Security for Full Virtualization Technologies<\/a><\/li>\n<\/ol>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

      Bu rehber, VMware Site Recovery Manager (SRM) i\u00e7in ara\u015ft\u0131rma yapan ekiplerin kurtarma plan\u0131 tasarlamas\u0131na odaklan\u0131r. Kaynak olarak verilen Protection and Recovery 9.1 belgesi; sanal makinelerin, a\u00e7\u0131l\u0131\u015f s\u0131ras\u0131n\u0131n ve a\u011f ayarlar\u0131n\u0131n bir kurtarma plan\u0131yla nas\u0131l d\u00fczenlendi\u011fini a\u00e7\u0131klar. \u0130\u015flem ad\u0131mlar\u0131n\u0131 kurulu \u00fcr\u00fcn ve s\u00fcr\u00fcmle e\u015fle\u015ftirin. Veri \u00e7o\u011faltma, yedek saklama ve uygulama do\u011frulamas\u0131 ayr\u0131 sorumluluklar olmaya devam eder. […]<\/p>\n","protected":false},"author":3,"featured_media":1378,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[31,26,24,25],"tags":[86,124,125,123,99,126],"class_list":["post-803","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guvenlik","category-bilgi-islem","category-bulut-danismanlik-hizmeti","category-buluta-genel-bakis","tag-guvenlik","tag-raporlama-ve-izleme","tag-site-recovery-manager","tag-srm","tag-vmware","tag-vmware-srm"],"_links":{"self":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/803","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/comments?post=803"}],"version-history":[{"count":3,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/803\/revisions"}],"predecessor-version":[{"id":848,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/posts\/803\/revisions\/848"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/media\/1378"}],"wp:attachment":[{"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/media?parent=803"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/categories?post=803"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fibacloud.com\/tr\/kaynaklar\/wp-json\/wp\/v2\/tags?post=803"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}