Answer
Any HYCU Users Here?
We are currently evaluating Nutanix and also HYCU for backup. So far HYCU looks really good running on my CE lab server but there is one issue that they cannot answer to. For file restores on older recovery points (past the "Fast Restore" point), HYCU must copy the entire VM from the storage target and mount it to even start the search for a file. While for small VM's this my not be a big deal, larger VM's would cause a wait time based on your network connection to the storage target. For anyone using HYCU is this a concern to you? I'm very interested in hearing real world feed back here. Thanks!
Best answer by MMSW_DE
Hi,
we ran into the exact same issue in our production environment: Restoring a multi-Terabyte Exchange VM took many hours while cluster overall performance (we use entry-level 1000-NX series hardware) was clearly affected by sustained bulk writes.
We simply decided to keep more Fast Restore points (i.e. cluster based snapshots), reaching further into the past. Storagewise this workaround should not be a big deal, although there is no way to see how large those snaphots actually are.
I'm very confident the folks at Hycu will eventually establish a solution for this.
we ran into the exact same issue in our production environment: Restoring a multi-Terabyte Exchange VM took many hours while cluster overall performance (we use entry-level 1000-NX series hardware) was clearly affected by sustained bulk writes.
We simply decided to keep more Fast Restore points (i.e. cluster based snapshots), reaching further into the past. Storagewise this workaround should not be a big deal, although there is no way to see how large those snaphots actually are.
I'm very confident the folks at Hycu will eventually establish a solution for this.
This topic has been closed for replies.
Hi,
we ran into the exact same issue in our production environment: Restoring a multi-Terabyte Exchange VM took many hours while cluster overall performance (we use entry-level 1000-NX series hardware) was clearly affected by sustained bulk writes.
We simply decided to keep more Fast Restore points (i.e. cluster based snapshots), reaching further into the past. Storagewise this workaround should not be a big deal, although there is no way to see how large those snaphots actually are.
I'm very confident the folks at Hycu will eventually establish a solution for this.
we ran into the exact same issue in our production environment: Restoring a multi-Terabyte Exchange VM took many hours while cluster overall performance (we use entry-level 1000-NX series hardware) was clearly affected by sustained bulk writes.
We simply decided to keep more Fast Restore points (i.e. cluster based snapshots), reaching further into the past. Storagewise this workaround should not be a big deal, although there is no way to see how large those snaphots actually are.
I'm very confident the folks at Hycu will eventually establish a solution for this.
Thanks for the response
As for exchange, I have not tested this yet but I'm assuming like SQL, you can restore the database without re-hydration. Is that your experience?
Also, are you using Nutanix Files? If so, are there any gotcha's with HYCU here?
I'm sorry, I didn't do the Exchange restore tests myself and I frankly don't know how far my colleague got. We are not yet using Nutanix files, so I'm afraid no experience there either.
Generally speaking, Hycu's integration is very good and they are highly motivated to make things work.
Generally speaking, Hycu's integration is very good and they are highly motivated to make things work.
We have transcended this limitation with HYCU 4.1. You no longer have to restore an entire VM from a remote backup target (Onprem or Cloud) in order to just recover a couple of files. With HYCU 4.2, this applies to application level recovery. For example, you don’t have restore an entire MSSQL VM just to recover an individual MSSQL database at specific point in time.
+3When i was at A3 we where running HYCU for about 3 years with
Warm recommendation from me :)
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.