How to restore Symantec Powerquest V2i backup files
I received a set of V2i backup files and after much digging around on the internet i found that these files where created using Powerquests backup software. However, it looks like Powerquest is no more, Symantec bought them, and incorporated their software into some of it's own products. I haven't been able to find a product provided by Symantec that will let me restore these files. I spoke with a sales rep at Symantec who told me that they don't support that file extension anymore.
Does anyone know what program i can use that will let me view/restore these V2i files? I found a website that sells out-dated software where i can buy the original Powerquest software but i would rather buy a new program rather than one that's 6 years old.
Does anyone know what program i can use that will let me view/restore these V2i files? I found a website that sells out-dated software where i can buy the original Powerquest software but i would rather buy a new program rather than one that's 6 years old.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
From what I could gather, the following happened (simplified version):
When Symantec purchased Powerquest, the .v2i technology was incorporated into Norton Ghost, the old .gho technology abandoned. So theoretically, all Ghost versions from 2004 on should be able to process .v2i files.
You can download a free 30-day trial of the newest Ghost version to check this: http://nct.symantecstore.com/fulfill/0184.074
On top of this, Symantec started to create a whole new product formerly called "Symantec LiveState Recovery", now "Backup Exec System Recovery". If you browse the product related forums (https://forums.symantec.com/syment?category.id=besr) you will realize that this may be the product you're looking for, because searching for .v2i yields many hits and there are definitely users who created such files only this month.
So the statement by the Symantec employee you spoke to was either wrong or purposefully misleading.
Hope this helps.