Video Screencast Help

Customer-specific catalog backups

Created: 28 Aug 2012 | 2 comments
John_Nardello's picture
1 Agree
0 Disagree
+1 1 Vote
Login to vote

For multi-tenant environments it would be extremely helpful to be able to generate a catalog backup specific to a given set of clients. For example if clientA, clientB, & clientC all belonged to the same customer and a catalog backup was run for them, the EMM database would only include the image headers for those clients, volume pools those clients have tapes in, their policy info, STUs used by their policies, etc. Likewise the images directory would only contain the specific directories for these clients. This would speed up customer-specific DRs immensely as well as eliminate any of our concerns about exposing other customer's data (or even the fact that a given customer's competitors may also be our customers, which is often apparently just from our policy naming convention).

While some of this is probably scriptable it wouldn't be particularly easy to do everything required, plus the difficulty in deleting other customer's data from EMM.

Comments 2 CommentsJump to latest comment

RadovanTuran's picture

As I know EMM doesn't keep any image related information. Image database is still in folder structure. You can backup list of folders within /usr/openv/netbackup/db/images/

0
Login to vote
John_Nardello's picture

And that's what we're currently doing - flatfile backups of the appropriate image folders. Sometimes we'll even export & reimport EMM data depending on what's going on. But it's certainly not a hands-off process.

 

- "Your backups are only as good as your restores."

0
Login to vote