>On one of our implementations we have a storage pool which is getting
>refreshed everyday, full backup.  and we need
>to archive each day of that primary pool and save it for 30 days.  The copy
>pool will be having same retention as primary, right?
>I'm not sure, is there a way to assign different MC to the copy pool?

Yes, the copy storage pool is just another image of the same data, under
the same policies, so has the same retention.  No, there's not such thing
as management classes for copy storage pools.

It's not clear what you really mean about archiving the primary pool.
I think what you're getting at is the whole Disaster Recovery topic,
and the standard practice of sending copy storage pool tapes offsite.
Depending upon the speed with which you can get the data back from
offsite (be it courier-carried tapes, or networked access), you may or
may not want to have an on-site copy storage pool.  That is, if a tape
in your primary storage pool exhibits read errors, you need to recover
the files that fell victim to the bad spot on the tape.  If you have
an on-site copy storage pool, that's quickly accomplished; but if it's
an off-site copy storage pool, you'd have to await the return of the
data.  If the delay in getting the data returned to your site isn't
bad, you can afford to not have a local copy storage pool and just
depend upon the off-site one.  You could also consider using the
Backup Set facility to make a portable image of your current Active
backup files.

   Richard Sims, BU