Video Screencast Help

EV and Backup Exec Migrator

Created: 13 Jun 2013 • Updated: 13 Jun 2013 | 4 comments
KeirL's picture
This issue has been solved. See solution.

Hi

Can anyone help me understand how backup exec migrator should work? I'm finding the Backup Exec admin guide very confusing.

So Backup Exec Migrator is all configured correctly and migrating data from EV into Backup Exec. I've configured the collections and can see EV creating the .CAB files, the DVS etc files have all been deleted and I can still recall placefolders from the file server (which I assume is from the .CAB files just using the 'collections' functionality. Backup Exec has run a backup job and has backed up the .CAB files using the 'Backup Exec Migrator' feature.

Now (and I may be wrong) is that I think the next thing to happen will be that EV will delete the .CAB files a few days after they have been migrated into Backup Exec. This hasn't happened yet but is configured to happen in a couple of days.

I was then reading about how the files are retrieved should a user recall a placeholder that has been collected into a .cab file and subsequently migrated into Backup Exec....... the BUE admin guide says the below:

"All file retrieve operations start from the Enterprise Vault server console. You cannot restore archived Enterprise Vault data from Backup Exec.

When files are migrated from a partition, Enterprise Vault creates a shortcut in the partition that replaces the migrated file. The shortcut also links to the storage location of the migrated file. You retrieve files by double-clicking their shortcuts in the Enterprise Vault partition itself. If a partition retains a local copy of the migrated files, Enterprise Vault retrieves the files from the local copies. If Enterprise Vault deletes the migrated files because the partition's file retention period passes, the requested files must be retrieved from Backup Exec storage media."
 
I don't really get it....... When is says "When files are migrated from a partition, Enterprise Vault creates a shortcut in the partition that replaces the migrated file.does that refer to Vault Store Partitions?? So does EV try to restore the .CAB file but this has been replaced by a shortcut pointing to Backup Exec when subsequently starts a restore of the .CAB file back on the EV Partition?
Then it says "You retrieve files by double-clicking their shortcuts in the Enterprise Vault partition itself." Who does? surely I'm not expected to navigate through the Vault store partitions and manually double click on the .cab shortcuts to initate a restore from backup exec..... how will I know which .cab file I need?
 
I think I must have the wrong end of the stick here but could do with a bit of advice on what should happen so I can ensure it's working correctly.
 
kind regards
KL
Discussion Filed Under:

Comments 4 CommentsJump to latest comment

AndrewB's picture

well, it looks like that document could be improved. the jist of it is this:

when you retrieve an archived item, EV goes and looks for it, right? if it's been migrated it knows to go to BE and then BE will have a job that says go insert this tape or whatever the case may be. it's really not that complicated if you look at it from a high level.

HOWEVER, there are so many caveats to migrating to NBU or BE that it's generally not recommended. there are plenty of forum posts where all of the Trusted Advisors share there thoughts on this topic and the consensus is clear.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

SOLUTION
KeirL's picture

Hi Andrew

thanks for the fast reply - I think it was that high level view that I need to help me on my way. 

From an end user perspective my understanding is that they would still see the placeholders on the file server as normal, they would then double click to open the file they want and this would initiate a recall from EV. EV would then recall the file from either DV files or .cab file (if it has already been part of a collection).

If the file was indeed held within a cabinet file it would look to extract the cabinet file back and recall the requested file back to the user. However, If the required cabinet file had been migrated into Backup Exec and the cab file subsequently had been deleted by EV (the cab file does get deleted if configured that way doesn't it?) then Backup Exec will get told to restore the cabinet file so EV can then complete the extraction and finally deliverl the file back to the end user?

All this requires no manual intervention from the EV\backup administators (with perhaps the exception of inserting a tape) and certainly doesn't need anyone double clicking on shortcuts in Vault Store partitions?

And is also seemless to the end user  - perhaps with the exception of them having to find a good book to read.

Thanks

Keir

AndrewB's picture

that is all correct. it's completely transparent to the end user except for, like you said, the long delay for retrieval of the archived item; especially if BE is waiting for a tape to be inserted.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

KeirL's picture

That's great - thanks very much

and I agree with your thoughts on the BUE admin guide perhaps could be written in a somehwat clearer manner..... some may say it's 'borderline wrong'  :o) 

cheers