Case ID 05071285
Has anyone see behavior where installing Vormetric encryption onto a repository server breaks the ability to do a Windows guest file restore? Simply installing Vormetric does the damage and I THINK that Vormetric is intercepting file system calls which end up blocking the ability of Veeam to mount the backup where it is accessible from the Backup Browser or the VeeamFLR folder on the server. The actual displayed error is "unable to mount disk: unsupported disk type". Note that we are NOT attempting to encrypt the Veeam backups with Vormetric and we didn't even have to define any guardpoints to cause the issue.
I have a large HP Apollo server and needed to temporarily store some files for a customer which they needed encrypted so we installed Vormetric as was their standard and then discovered the FLR was broken some time later, much to our surprise. I was able to do the restore by copying the backup to a different server so I have a workaround but are curious to see if the 2 products can co-exist and if anybody has seen a similar issue.
-
- Enthusiast
- Posts: 28
- Liked: 2 times
- Joined: Jan 14, 2013 6:40 pm
- Full Name: Sloan Essman
- Location: Houston, TX
- Contact:
CipherTrust Vormetric blocks Windows Guest File restore
Sloan Essman
Lead Specialist - Backups and Data Protection
Energy Transfer Partners
Lead Specialist - Backups and Data Protection
Energy Transfer Partners
-
- Veeam Software
- Posts: 3649
- Liked: 610 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: CipherTrust Vormetric blocks Windows Guest File restore
Hi Sloan,
Basically, if the root cause is related to the system calls intercepted by 3rd-party application, I'll have a lot of doubts about the possibility to fix it at the level of our code. In the meantime, I suggest to continue working with our support team in order to prove or refute the hypothesis about system calls. By the way, process monitor tool could hep to get a full trace of all system calls. However, you should use it only under the guidance of our support team.
Thanks!
Basically, if the root cause is related to the system calls intercepted by 3rd-party application, I'll have a lot of doubts about the possibility to fix it at the level of our code. In the meantime, I suggest to continue working with our support team in order to prove or refute the hypothesis about system calls. By the way, process monitor tool could hep to get a full trace of all system calls. However, you should use it only under the guidance of our support team.
Thanks!
Who is online
Users browsing this forum: Baidu [Spider] and 30 guests