One profile to access multiple pools

Tandeo

One pool connection can only use one access profile.  The access profile will have only 1 home virtual pool which it will write content to but it may be granted read access rights to other virtual pools in the cluster.

Hi Paul,

Thanks for the tip. let me give you some more details.

My app will archive files to different pools each set with a specific retention period on our prod box.

These pools will then be replicated to another box at a DR site.

So basically here, from what you say, I will need to create a pea file for each profile/pool setup on prod -> same for each replicated pools ->  merge the pea files for each pool/profile(prod and DR) -> give that merged pea file of each pool to my app.

Please correct me if i'm wrong... still new to centera (1 month)

Creating a different virtual pool for each different retention period seems a bit overkill to me.  Why not just create them with a different retention period or retention class.  Untimately doing it your way would not scale beyonds 10's of different retention periods.

So I'm curious, why do it this way?

Ok got your point here.

But one more precision, the retention period is managed by the app and i'm not the app guy, i'm just the storage admin.

First I thought of creating just one big pool with no retention and give it to the app. Then he came to me and requested if he could have different pools for each retention as this would ease administration. That's why my initial question was if I could use the same profile to access all the pools.

At the end I think we we will set up retention on the pools at centera level to be able to reclaim space but for the time being we are just concentrating on the app level. We may at most need 4 different retention periods.

Would be of great help if someone has already done this and provide his views...

Is the application yours?  If not what is it?

If it's yours then the application developer is going to have a harder time coding for multiple pool connections rather than just setting the retention period or class.

You can of course have say 4 different instances of your application running instead but that may or may not be easy for you to  do.

If you can't or won't have the app set the retention period/class then yes you could set up say 4 VP each with their own default retention period and as long as the app doesnt specify a retention period then the clips will pick up the default.  HOwever this will need careful setup particularly if you want to be able to access all clips from one access profile

You comment

At the end I think we we will set up retention on the pools at centera level to be able to reclaim space

I'm not sure I understand.

Hi Paul,

Application is IBM OnDemand and TSM to access storage.

: 'set up retention on the pools at centera level to be able to reclaim space' - We do not have any compliance or regulations enforced for the retention periods of the data. So we are going to decide on retentions older than the app retention at storage level. Once the clips are expired at pool retention level we will then be able to reclaim the space through the garbage collection process.

Have a meeting with the app(IBM) guys to decide on the final strategy. Will keep you updated....

Paul

How do I grant access to additional pools ?

By using Centera Viewer to provide appropriate a profile with appropriate read access to the pools required. Please see the HTML "Online Help" documentation that comes with the CentraStar tools / customer CD.