The only way its really possible is to set up an isolated machine with SQL and EV installed, restore the EnterpriseVaultDirectory and the users vault store (or vault stores if using OSIS) and then restore the entire data.
Get everything back and pointed to the local drives (such as the PartitionRootPath to be your local restored data directory) and make sure things like the site alias, and EV Server Alias are all pointing to that new machine in something like the hosts file.
then when you get EV up and running do an export of the users archive to a PST
So the way's i've done it before are as follows
1. Note down the EVSite Alias and the EV Server Alias and Computer Name for the live server
2. Set up a server that has SQL Server/IIS/MSMQ etc installed
3. Ensure you have a user thats a local admin and has sufficient SQL Rights (Don't worry about Exchange or anything else)
4. Edit the c:\windows\system32\drivers\etc\hosts file and point everything at the local machine, such as:
evsite 127.0.0.1
evserver1 127.0.0.1
myServer.myDomain.com 127.0.0.1
myServer 127.0.0.1
mySQLServer.myDomain.com 127.0.0.1
mySQLServer 127.0.0.1
5. Install Enterprise Vault to the same Service Pack level as from when you are going from the backups
(for instance if you were on EV8 SP2 in December but you're now on EV8 SP3, install EV8 SP2)
6. Restore the SQL Databases (EnterpriseVaultDirectory, EVVaultStore and FingerPrint database to local sql server)
7. Restore the EV Data (Just Vault Store Partitions, don't worry about the indexes) to a drive accessible by that machine
8. Open the EnterpriseVaultDirectory database and edit the PartitionEntry table and change the PartitionRootPaths to be where your restore data is
For instance change from something like \\mySANServer\EVPtn1 to E:\Vault Stores\EVPtn1\
9. Now run the Enterprise Vault Configuration utility and tell it to create a databasse on your local sql server
10. It will then say that it found the computer in the database and ran repairs
11. Start the EV Admin Service, Directory Service and Storage Service
12. Stop the Shopping, Indexing and Task Controllers if they're started
13. Put the Vault Stores in to read only mode
14. Export the user
The reason we want to change the names in the database and the hosts file and what not is so that we do not risk affecting live data.
The more isolated this set up can be, the better