build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | format run

$ soultec get post/vsan-data-protection -o yaml$ soultec get post/vsan-data-protection -o json$ soultec get post/vsan-data-protection -o toml$ soultec get post/vsan-data-protection -o xml$ python3 vsan-data-protection.pyPS> ./vsan-data-protection.ps1$ go run vsan-data-protection.go$ node vsan-data-protection.js

apiVersion: soultec.ch/v1kind: Postmetadata: name: vsan-data-protection locale: en labels: author: daniel-stadelmann series: how-to capability/storage: 2.36 capability/backup-recovery: 2.14 capability/security: 1.91 vendor/vmware: 0.98 annotations: source: blog-content/posts/en/vsan-data-protection.md route: /en/insights/vsan-data-protection/ schema: /nerd/schema/posts.json markdown: /en/insights/vsan-data-protection.mdspec: title: vSAN Data Protection date: 2025-03-13 author: daniel-stadelmann locale: en summary: >- vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly. capabilities: [storage, backup-recovery, security] vendors: [vmware] series: how-to hero: /blog-assets/vsan-data-protection/hero.webp migrated: 2026-08-24 translationReviewed: false draft: false sections: - body: | With [vSAN](https://soultec.ch/solutions/vmware/vmware-cloud-foundation/vmware-vsan/) 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you. [vSAN Data Protection](https://blogs.vmware.com/cloud-foundation/2024/08/02/superior-snapshots-using-vmware-vsan-data-protection/) is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either. Thanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM's performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? [Get in touch](https://soultec.ch/contact-us/). ![](/blog-assets/vsan-data-protection/01.webp) Beyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time. The whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a "Protection Groups" tab where the actual protection groups are created, and a "VMs" tab listing every VM on the vSAN with its protection status. ![](/blog-assets/vsan-data-protection/02.webp) Protection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable. ![](/blog-assets/vsan-data-protection/03.webp) The schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels. ![](/blog-assets/vsan-data-protection/04.webp) Interested? [Get in touch](https://soultec.ch/contact-us/) and we will happily do a demo or a PoC.status: corpus: 315 alsoLike: - {ref: posts/how-to-deploy-vsan-snapshot-service-appliance, score: 0.79} - {ref: posts/exagrid, score: 0.59} - {ref: experts/steven-rodenburg, score: 0.53} search: /en/search.json
{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "vsan-data-protection", "locale": "en", "labels": { "author": "daniel-stadelmann", "series": "how-to", "capability/storage": 2.36, "capability/backup-recovery": 2.14, "capability/security": 1.91, "vendor/vmware": 0.98 }, "annotations": { "source": "blog-content/posts/en/vsan-data-protection.md", "route": "/en/insights/vsan-data-protection/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/vsan-data-protection.md" } }, "spec": { "title": "vSAN Data Protection", "date": "2025-03-13", "author": "daniel-stadelmann", "locale": "en", "summary": "vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly.", "capabilities": [ "storage", "backup-recovery", "security" ], "vendors": [ "vmware" ], "series": "how-to", "hero": "/blog-assets/vsan-data-protection/hero.webp", "migrated": "2026-08-24", "translationReviewed": false, "draft": false, "sections": [ { "body": "With [vSAN](https://soultec.ch/solutions/vmware/vmware-cloud-foundation/vmware-vsan/) 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you.\n\n[vSAN Data Protection](https://blogs.vmware.com/cloud-foundation/2024/08/02/superior-snapshots-using-vmware-vsan-data-protection/) is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either.\n\nThanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM's performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? [Get in touch](https://soultec.ch/contact-us/).\n\n![](/blog-assets/vsan-data-protection/01.webp)\n\nBeyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time.\n\nThe whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a \"Protection Groups\" tab where the actual protection groups are created, and a \"VMs\" tab listing every VM on the vSAN with its protection status.\n\n![](/blog-assets/vsan-data-protection/02.webp)\n\nProtection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable.\n\n![](/blog-assets/vsan-data-protection/03.webp)\n\nThe schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels.\n\n![](/blog-assets/vsan-data-protection/04.webp)\n\nInterested? [Get in touch](https://soultec.ch/contact-us/) and we will happily do a demo or a PoC." } ] }, "status": { "corpus": 315, "alsoLike": [ { "ref": "posts/how-to-deploy-vsan-snapshot-service-appliance", "score": "0.79" }, { "ref": "posts/exagrid", "score": "0.59" }, { "ref": "experts/steven-rodenburg", "score": "0.53" } ], "search": "/en/search.json" }}
apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "vsan-data-protection"locale = "en"[metadata.labels]author = "daniel-stadelmann"series = "how-to""capability/storage" = 2.36"capability/backup-recovery" = 2.14"capability/security" = 1.91"vendor/vmware" = 0.98[metadata.annotations]source = "blog-content/posts/en/vsan-data-protection.md"route = "/en/insights/vsan-data-protection/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/vsan-data-protection.md"[spec]title = "vSAN Data Protection"date = 2025-03-13author = "daniel-stadelmann"locale = "en"summary = "vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly."capabilities = ["storage", "backup-recovery", "security"]vendors = ["vmware"]series = "how-to"hero = "/blog-assets/vsan-data-protection/hero.webp"migrated = 2026-08-24translationReviewed = falsedraft = false[[spec.sections]]body = '''With [vSAN](https://soultec.ch/solutions/vmware/vmware-cloud-foundation/vmware-vsan/) 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you.[vSAN Data Protection](https://blogs.vmware.com/cloud-foundation/2024/08/02/superior-snapshots-using-vmware-vsan-data-protection/) is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either.Thanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM's performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? [Get in touch](https://soultec.ch/contact-us/).![](/blog-assets/vsan-data-protection/01.webp)Beyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time.The whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a "Protection Groups" tab where the actual protection groups are created, and a "VMs" tab listing every VM on the vSAN with its protection status.![](/blog-assets/vsan-data-protection/02.webp)Protection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable.![](/blog-assets/vsan-data-protection/03.webp)The schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels.![](/blog-assets/vsan-data-protection/04.webp)Interested? [Get in touch](https://soultec.ch/contact-us/) and we will happily do a demo or a PoC.'''[status]corpus = 315search = "/en/search.json"[[status.alsoLike]]ref = "posts/how-to-deploy-vsan-snapshot-service-appliance"score = "0.79"[[status.alsoLike]]ref = "posts/exagrid"score = "0.59"[[status.alsoLike]]ref = "experts/steven-rodenburg"score = "0.53"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>vsan-data-protection</name> <locale>en</locale> <labels> <author>daniel-stadelmann</author> <series>how-to</series> <entry key="capability/storage">2.36</entry> <entry key="capability/backup-recovery">2.14</entry> <entry key="capability/security">1.91</entry> <entry key="vendor/vmware">0.98</entry> </labels> <annotations> <source>blog-content/posts/en/vsan-data-protection.md</source> <route>/en/insights/vsan-data-protection/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/vsan-data-protection.md</markdown> </annotations> </metadata> <spec> <title>vSAN Data Protection</title> <date>2025-03-13</date> <author>daniel-stadelmann</author> <locale>en</locale> <summary>vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly.</summary> <capabilities> <item>storage</item> <item>backup-recovery</item> <item>security</item> </capabilities> <vendors> <item>vmware</item> </vendors> <series>how-to</series> <hero>/blog-assets/vsan-data-protection/hero.webp</hero> <migrated>2026-08-24</migrated> <translationReviewed>false</translationReviewed> <draft>false</draft> <sections> <section> <body>With [vSAN](https://soultec.ch/solutions/vmware/vmware-cloud-foundation/vmware-vsan/) 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you.[vSAN Data Protection](https://blogs.vmware.com/cloud-foundation/2024/08/02/superior-snapshots-using-vmware-vsan-data-protection/) is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either.Thanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM's performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? [Get in touch](https://soultec.ch/contact-us/).![](/blog-assets/vsan-data-protection/01.webp)Beyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time.The whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a "Protection Groups" tab where the actual protection groups are created, and a "VMs" tab listing every VM on the vSAN with its protection status.![](/blog-assets/vsan-data-protection/02.webp)Protection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable.![](/blog-assets/vsan-data-protection/03.webp)The schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels.![](/blog-assets/vsan-data-protection/04.webp)Interested? [Get in touch](https://soultec.ch/contact-us/) and we will happily do a demo or a PoC. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <alsoLike> <item> <ref>posts/how-to-deploy-vsan-snapshot-service-appliance</ref> <score>0.79</score> </item> <item> <ref>posts/exagrid</ref> <score>0.59</score> </item> <item> <ref>experts/steven-rodenburg</ref> <score>0.53</score> </item> </alsoLike> <search>/en/search.json</search> </status></manifest>
# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "vsan-data-protection", "locale": "en", "labels": { "author": "daniel-stadelmann", "series": "how-to", "capability/storage": 2.36, "capability/backup-recovery": 2.14, "capability/security": 1.91, "vendor/vmware": 0.98, }, "annotations": { "source": "blog-content/posts/en/vsan-data-protection.md", "route": "/en/insights/vsan-data-protection/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/vsan-data-protection.md", }, }, "spec": { "title": "vSAN Data Protection", "date": "2025-03-13", "author": "daniel-stadelmann", "locale": "en", "summary": "vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly.", "capabilities": ["storage", "backup-recovery", "security"], "vendors": ["vmware"], "series": "how-to", "hero": "/blog-assets/vsan-data-protection/hero.webp", "migrated": "2026-08-24", "translationReviewed": False, "draft": False, "sections": [ { "body": ( "With [vSAN](https://soultec.ch/solutions/vmware/vmware-cloud-foundation/vmware-vsan/) 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you.\n" "\n" "[vSAN Data Protection](https://blogs.vmware.com/cloud-foundation/2024/08/02/superior-snapshots-using-vmware-vsan-data-protection/) is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either.\n" "\n" "Thanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM's performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? [Get in touch](https://soultec.ch/contact-us/).\n" "\n" "![](/blog-assets/vsan-data-protection/01.webp)\n" "\n" "Beyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time.\n" "\n" "The whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a \"Protection Groups\" tab where the actual protection groups are created, and a \"VMs\" tab listing every VM on the vSAN with its protection status.\n" "\n" "![](/blog-assets/vsan-data-protection/02.webp)\n" "\n" "Protection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable.\n" "\n" "![](/blog-assets/vsan-data-protection/03.webp)\n" "\n" "The schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels.\n" "\n" "![](/blog-assets/vsan-data-protection/04.webp)\n" "\n" "Interested? [Get in touch](https://soultec.ch/contact-us/) and we will happily do a demo or a PoC." ), }, ], }, "status": { "corpus": 315, "alsoLike": [ { "ref": "posts/how-to-deploy-vsan-snapshot-service-appliance", "score": "0.79", }, { "ref": "posts/exagrid", "score": "0.59", }, { "ref": "experts/steven-rodenburg", "score": "0.53", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))
# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Post' metadata = [ordered]@{ name = 'vsan-data-protection' locale = 'en' labels = [ordered]@{ author = 'daniel-stadelmann' series = 'how-to' 'capability/storage' = 2.36 'capability/backup-recovery' = 2.14 'capability/security' = 1.91 'vendor/vmware' = 0.98 } annotations = [ordered]@{ source = 'blog-content/posts/en/vsan-data-protection.md' route = '/en/insights/vsan-data-protection/' schema = '/nerd/schema/posts.json' markdown = '/en/insights/vsan-data-protection.md' } } spec = [ordered]@{ title = 'vSAN Data Protection' date = '2025-03-13' author = 'daniel-stadelmann' locale = 'en' summary = 'vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly.' capabilities = @('storage', 'backup-recovery', 'security') vendors = @('vmware') series = 'how-to' hero = '/blog-assets/vsan-data-protection/hero.webp' migrated = '2026-08-24' translationReviewed = $false draft = $false sections = @( [ordered]@{ body = @'With [vSAN](https://soultec.ch/solutions/vmware/vmware-cloud-foundation/vmware-vsan/) 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you.[vSAN Data Protection](https://blogs.vmware.com/cloud-foundation/2024/08/02/superior-snapshots-using-vmware-vsan-data-protection/) is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either.Thanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM's performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? [Get in touch](https://soultec.ch/contact-us/).![](/blog-assets/vsan-data-protection/01.webp)Beyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time.The whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a "Protection Groups" tab where the actual protection groups are created, and a "VMs" tab listing every VM on the vSAN with its protection status.![](/blog-assets/vsan-data-protection/02.webp)Protection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable.![](/blog-assets/vsan-data-protection/03.webp)The schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels.![](/blog-assets/vsan-data-protection/04.webp)Interested? [Get in touch](https://soultec.ch/contact-us/) and we will happily do a demo or a PoC.'@ } ) } status = [ordered]@{ corpus = 315 alsoLike = @( [ordered]@{ ref = 'posts/how-to-deploy-vsan-snapshot-service-appliance' score = '0.79' } [ordered]@{ ref = 'posts/exagrid' score = '0.59' } [ordered]@{ ref = 'experts/steven-rodenburg' score = '0.53' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32
// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": map[string]any{ "name": "vsan-data-protection", "locale": "en", "labels": map[string]any{ "author": "daniel-stadelmann", "series": "how-to", "capability/storage": 2.36, "capability/backup-recovery": 2.14, "capability/security": 1.91, "vendor/vmware": 0.98, }, "annotations": map[string]any{ "source": "blog-content/posts/en/vsan-data-protection.md", "route": "/en/insights/vsan-data-protection/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/vsan-data-protection.md", }, }, "spec": map[string]any{ "title": "vSAN Data Protection", "date": "2025-03-13", "author": "daniel-stadelmann", "locale": "en", "summary": "vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly.", "capabilities": []any{"storage", "backup-recovery", "security"}, "vendors": []any{"vmware"}, "series": "how-to", "hero": "/blog-assets/vsan-data-protection/hero.webp", "migrated": "2026-08-24", "translationReviewed": false, "draft": false, "sections": []any{ map[string]any{ "body": "With [vSAN](https://soultec.ch/solutions/vmware/vmware-cloud-foundation/vmware-vsan/) 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you.\n" + "\n" + "[vSAN Data Protection](https://blogs.vmware.com/cloud-foundation/2024/08/02/superior-snapshots-using-vmware-vsan-data-protection/) is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either.\n" + "\n" + "Thanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM's performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? [Get in touch](https://soultec.ch/contact-us/).\n" + "\n" + "![](/blog-assets/vsan-data-protection/01.webp)\n" + "\n" + "Beyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time.\n" + "\n" + "The whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a \"Protection Groups\" tab where the actual protection groups are created, and a \"VMs\" tab listing every VM on the vSAN with its protection status.\n" + "\n" + "![](/blog-assets/vsan-data-protection/02.webp)\n" + "\n" + "Protection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable.\n" + "\n" + "![](/blog-assets/vsan-data-protection/03.webp)\n" + "\n" + "The schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels.\n" + "\n" + "![](/blog-assets/vsan-data-protection/04.webp)\n" + "\n" + "Interested? [Get in touch](https://soultec.ch/contact-us/) and we will happily do a demo or a PoC.", }, }, }, "status": map[string]any{ "corpus": 315, "alsoLike": []any{ map[string]any{ "ref": "posts/how-to-deploy-vsan-snapshot-service-appliance", "score": "0.79", }, map[string]any{ "ref": "posts/exagrid", "score": "0.59", }, map[string]any{ "ref": "experts/steven-rodenburg", "score": "0.53", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}
// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Post", metadata: { name: "vsan-data-protection", locale: "en", labels: { author: "daniel-stadelmann", series: "how-to", "capability/storage": 2.36, "capability/backup-recovery": 2.14, "capability/security": 1.91, "vendor/vmware": 0.98, }, annotations: { source: "blog-content/posts/en/vsan-data-protection.md", route: "/en/insights/vsan-data-protection/", schema: "/nerd/schema/posts.json", markdown: "/en/insights/vsan-data-protection.md", }, }, spec: { title: "vSAN Data Protection", date: "2025-03-13", author: "daniel-stadelmann", locale: "en", summary: "vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly.", capabilities: ["storage", "backup-recovery", "security"], vendors: ["vmware"], series: "how-to", hero: "/blog-assets/vsan-data-protection/hero.webp", migrated: "2026-08-24", translationReviewed: false, draft: false, sections: [ { body: "With [vSAN](https://soultec.ch/solutions/vmware/vmware-cloud-foundation/vmware-vsan/) 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you.\n" + "\n" + "[vSAN Data Protection](https://blogs.vmware.com/cloud-foundation/2024/08/02/superior-snapshots-using-vmware-vsan-data-protection/) is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either.\n" + "\n" + "Thanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM's performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? [Get in touch](https://soultec.ch/contact-us/).\n" + "\n" + "![](/blog-assets/vsan-data-protection/01.webp)\n" + "\n" + "Beyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time.\n" + "\n" + "The whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a \"Protection Groups\" tab where the actual protection groups are created, and a \"VMs\" tab listing every VM on the vSAN with its protection status.\n" + "\n" + "![](/blog-assets/vsan-data-protection/02.webp)\n" + "\n" + "Protection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable.\n" + "\n" + "![](/blog-assets/vsan-data-protection/03.webp)\n" + "\n" + "The schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels.\n" + "\n" + "![](/blog-assets/vsan-data-protection/04.webp)\n" + "\n" + "Interested? [Get in touch](https://soultec.ch/contact-us/) and we will happily do a demo or a PoC.", }, ], }, status: { corpus: 315, alsoLike: [ { ref: "posts/how-to-deploy-vsan-snapshot-service-appliance", score: "0.79", }, { ref: "posts/exagrid", score: "0.59", }, { ref: "experts/steven-rodenburg", score: "0.53", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 64 lines · YAML · validated at build# 65 lines · JSON · validated at build# 77 lines · TOML · validated at build# 89 lines · XML · validated at build# 89 lines · Python · read back at build, equals the JSON record# 86 lines · PowerShell · read back at build, equals the JSON record# 99 lines · Go · read back at build, equals the JSON record# 84 lines · JavaScript · read back at build, equals the JSON record · served at /en/insights/vsan-data-protection.md

How-To · 2025-03-13

vSAN Data Protection

vSAN 8 Update 3 brought the Data Protection feature, which closes the last gap against conventional block storage. You can now snapshot workloads on production storage directly.

2025-03-13Date
Daniel StadelmannAuthor
1Min read
Vendors VMware 0.98

With vSAN 8 Update 3, VMware released the Data Protection feature. It closes the last missing piece in the feature battle against conventional block storage. From now on you can snapshot your workloads directly on production storage, so in a disaster you restore the VM with a very short RTO and a far shorter RPO than a backup would give you.

vSAN Data Protection is also much more granular. You decide per VM how often a snapshot is taken and how long it is kept. Restoring from a snapshot brings no overhead of deleting, moving and cleaning up VMs either.

Thanks to the new vSAN ESA snapshot engine, snapshots no longer affect your VM’s performance. So there is no reason left not to use this. Do you have vSAN ESA but not Data Protection yet? Get in touch.

Beyond classic recovery, vSAN Data Protection covers ransomware recovery, recovering VMs from accidental deletion and, of course, cloning a VM from a point in time.

The whole thing is fully integrated into vCenter and driven from there. It shows at a glance what percentage of VMs is protected. There is a “Protection Groups” tab where the actual protection groups are created, and a “VMs” tab listing every VM on the vSAN with its protection status.

Protection groups allow dynamic membership, explicit selection or a combination of both. You can also define whether the vSAN snapshot for a group should be immutable.

The schedule can be set to whatever your IT service continuity management calls for. Anyone who knows VLCR (formerly VCDR) will see some parallels.

Interested? Get in touch and we will happily do a demo or a PoC.

You might also like