Anthony,

     What you suggest is copying my primary volumes and then bring the copy
     volumes offsite. Assuming that you mean copying backup-data, the
     copies will expire along with the primaries. What I want is:
     1) Having only backup-data in the library, and copies of backups
     offsite.
     2) Creating archives from backups in a separate pool.
     3) Setting volumes in the archive pool to offsite, and remove them
     from my library.

     I know that all archives will take up space in my database but that's
     OK.

     Hope this clarifies my wishes.

     Chris Roelofs
     Mainland Sequoia



______________________________ Reply Separator _________________________________
Subject: Re: Re[2]: Archive & offsite
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at inet-1
Date:    11/19/98 12:04


It can.  What you can do is create a copy storage pool.
These pools are designed to hold data copied from one pool to the other.
Once that data is copied to the copy storage pool, you can take those tapes
offsite.  Mark the volumes as being unavailable and there you are.  You can
then bring them back to the system as you please.  The only draw back is you
will have references to the data in the database that will take up space for
a long time.

Anthony Jones
Koch Industries, Inc.
Platform Technologist
316-828-2432

> -----Original Message-----
> From: Chris Roelofs [SMTP:Chris.J.Roelofs AT MAIL.ING DOT NL]
> Sent: Thursday, November 19, 1998 11:49 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re[2]: Archive & offsite
>
>      Hello all,
>
>      Wanda Prather wrote:
>
>      <quote>
>      You could use the Export function to do that.  Or, just open the
>      Properties of the tape you want to remove, and change its access mode
>      to "offsite". Then ADSM won't call for that tape again.  However, the
>      data base entries describing the tape and its contents will remain.
>      <unquote>
>
>      However, volumes in a primary pool aren't allowed to have an offsite
>      status, so...
>
>      Our site really wants to do a lot of archiving, for legal and other
>      purposes. But I also have to make backups, and now I'm having
> problems
>      archiving and backupping the same (!) data within the available
>      window.
>
>      IBM, why can't ADSM do some kind of backup-to-archive conversion for
>      specific data of a specific client at a specific time. And then allow
>      for offsite vaulting of volumes in an "archive storage pool"? All the
>      data I want to archive is already at the ADSM server in the form of
>      backup, so why not simply copy it?
>
>      Please comment on this idea.
>
>      Regards,
>
>      Chris Roelofs
>      Mainland Sequoia