Yes we should have better left it as it is by default: as a dependent disk. And if it's gonna take too long for that, i will switch to forward incrementals with synthetic fulls. 3TB of change, yeah, it'll take several hours, just leave enough space for snapshots. Incrementals are going to depend on how much changed, but if it's small it's usually not more than 10 minutes. It'll take some time but that's up to your storage really. I use Veeam for up to 20TB file servers, it doesn't care. Have you considered a dedicated SAN or NAS solution as a file server ? There are many enterprise grade NAS or 3 NAS solutions that I can suggest.NAS to NAS HA with backup to NAS. Part of the statement is is NEVER a good idea to have a human perform snapshot of VMs unless if is for a short time like for performing Windows updates or other critical updates and the snapshot is manually removed after updates is completed (best practice of not more than 72 hours).Ĥ. "Because im not really sure weather its a good idea to snapshot a VM of this size. Snapshots are a way to quiescence the VM.the only other way to quiescence a VM is to power it down.ģ. If you have a backup software and it uses VMware snapshots, let the backup software handle the snapshots and do not modify settings further. Some things are set as default for a reason (eg VMDK sector sizes, VM disks "independent or dependent", backup processes). Keep things simple and do not over think things. A few things I think some VM users may need to understand.ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |