Hi Veeam Team,
I have a question about cooperation of Veeam B&R + Nimble Storage.
You can create a job of Nimble Storage Snapshot only from Veeam.
In addition to Primary Storage, you can save snapshots with the Replicated Copy function to Secondary Storage.
This function is very convenient!!
However, Restore from Storage Snapshot only supports the following.
· Instant VM Recovery
· File Level restore
· Application Item Restore
Please let me know someone about the mechanism that Entire VM Restore can not do.
Storage Snapshot data is mounted on the ESXi host as storage when restoring.
Is it because only ESXi hosts have access to snapshots?
I am very happy that someone will save me.
Kind Regards,
Asahi,
Climb Inc.
-
- Expert
- Posts: 143
- Liked: 7 times
- Joined: Jun 03, 2016 5:44 am
- Full Name: Iio Asahi
- Location: Japan
- Contact:
-
- Enthusiast
- Posts: 82
- Liked: 11 times
- Joined: Nov 11, 2016 8:56 am
- Full Name: Oliver
- Contact:
Re: About Restore from Nimble Storage Snapshot
Where else do you want to attach your VMFS-Datastore from the Nimble Snapshot?
In this place the Instant VM Recovery is the best way to recover your VM from the Storage Snapshot.
In this place the Instant VM Recovery is the best way to recover your VM from the Storage Snapshot.
-
- Novice
- Posts: 9
- Liked: 1 time
- Joined: Aug 28, 2018 4:39 pm
- Full Name: Phil Jochum
- Contact:
Re: About Restore from Nimble Storage Snapshot
Asahi,
This is the method when restoring from a storage snapshot. When using traditional repositories (i.e. secondary storage targets with backup files), the "Entire VM" method copies the backup to a datastore that is accessible by the hypervisor which takes time.
When restoring from storage snapshots, the copy process is not needed since the recovery point that you are restoring already exists on the primary storage. Thus, all that is necessary for restoration is for Veeam to manage the snapshot mount and inventory addition processes at the hypervisor.
Technically, you could mount that snapshot to any other storage-attached host assuming it has a VMFS driver available, but why bother when Veeam is adding value by managing all of those processes for you?
~Phil
This is the method when restoring from a storage snapshot. When using traditional repositories (i.e. secondary storage targets with backup files), the "Entire VM" method copies the backup to a datastore that is accessible by the hypervisor which takes time.
When restoring from storage snapshots, the copy process is not needed since the recovery point that you are restoring already exists on the primary storage. Thus, all that is necessary for restoration is for Veeam to manage the snapshot mount and inventory addition processes at the hypervisor.
Technically, you could mount that snapshot to any other storage-attached host assuming it has a VMFS driver available, but why bother when Veeam is adding value by managing all of those processes for you?
~Phil
Who is online
Users browsing this forum: No registered users and 24 guests