Escapo IT wrote:Had a chance to retest this scenario and happy to report this seems fixed for me with 839.
Took a new backup (backup-to-tape), split over two LTO5 tapes, restore ~1TB vbk file to local filesystem. Compared filesize, they are identical. Was able to import the VBK file into Veeam, was able to "double-click" the VBK file to see the contents within Veeam, ran backup validator which showed no errors. Load of my mind !!
To the others reading this thread; The patch notes and the comments from Veeam here on the forums seem to indicate this is environment specific, in fact the whole tape ecosystem seems to be a minefield of slight variations depending on drive/library/manufacturer, so I would urge you to test this for yourself, even after applying patch 3a. A backup is worthless without the ability to restore it !!
We have certainly been guilty of being lazy in that regard but this has opened my eyes and I will push for better policies making regular checks mandatory, perhaps using something like SureBackup as a first step.
mazur1000 wrote:Yes. The latest patch solves the problem with restoring from tape backup is virtual machines created using veeam. If using veeam to backup and then restore individual files, the problem persists (ibm ts3200 lto 6)
Users browsing this forum: No registered users and 1 guest