May I suggest something ?
I had to deal with a problem like that, involving externalization of datas, for
legal archiving.
I made a specific node, specific mgmt class and archive datas like that, then
export node to deal with externalization of cartridges.
I keep node definition but I had deleted filespaces under it and freed db space
like that.
Data's are on export cartridge. It is easy to retrieve it with an "import node
dates=relative".
Regards,
Pierre
> -----Message d'origine-----
> De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De
> la part de Angus Macdonald
> Envoyé : lundi 22 octobre 2007 15:02
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : Re: [ADSM-L] Archiving basic queries
>
> That's the plan. I have an archiving storage pool setup and
> ready, although not a separate management class. The bit I'm
> working on is getting the existing backups of the files I'm
> archiving, out of the existing main storage pool. I can then
> reclaim the main storage pool tapes and regain a lot of library space.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On
> Behalf Of Larry Clark
> Sent: 22 October 2007 13:49
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Archiving basic queries
>
>
> Have you considered creating a separate managment class with
> its own archive pool, archive/deleteing your files to that,
> then checking out those volumes and storing them on a shelf someplace?
>
>
> ----- Original Message -----
> From: "Angus Macdonald" <Angus.Macdonald AT NWW-TR.WALES.NHS DOT UK>
> To: <ADSM-L AT VM.MARIST DOT EDU>
> Sent: Monday, October 22, 2007 7:41 AM
> Subject: Re: [ADSM-L] Archiving basic queries
>
>
> I may not be describing it very well ;-)
>
> I have lots of old, unaccessed files that need to be retained
> indefinitely.
> To free up library space I want to archive them to tape and
> delete from the
> fileservers. It would be nice if I could remove the Tivoli
> database entries
> for these files to free up the library sooner rather than later.
>
> I know how to select and archive only those files with a last
> accessed date
> earlier than some arbitrary date in the past. I was interested in the
> possibility of expiring only those files and not others from Tivoli
> afterwards.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On
> Behalf Of
> Richard Sims
> Sent: 22 October 2007 12:34
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Archiving basic queries
>
>
> On Oct 22, 2007, at 5:27 AM, Angus Macdonald wrote:
>
> > ...
> > The next query is expiration. Ideally, I'd like to immediately
> > expire the files which have been archived, to free up library
> > space. I currently retain 3 versions up to 100 days and the final
> > version up to 365 days. I can set all of those values temporarily
> > nice and low but as I understand it, the database objects are only
> > finally removed by the EXPIRE INVENTORY process at the server end.
> > This would presumably remove all old versions, not just those I
> > have archived.
> >
> > Is there a way around this, am I simply wrong, or will I just have
> > to wait for the normal expiration process timeout?
>
> I think we're all puzzled as to why you would have bothered archiving
> files which you could have simply deleted from the file system, to
> achieve the same effect?
>
> You need to dig into the B/A client manual, the chapter "Archiving
> and retrieving your data", which describes all the aspects and
> factors of file archiving - including deleting archive data. You
> need a solid grounding in the area that you are pursuing, in order to
> make best use of it. Going at it piecemeal is not a good approach
> when dealing with data retention regimens.
>
> Richard Sims http://people.bu.edu/rbs
>
> Gallai'r e-bost yma gynnwys gwybodaeth gyfrinachol a/neu ddeunydd
> hawlfraint. Os ydych chi'n meddwl eich bod wedi derbyn yr
> e-bost yma drwy
> gamgymeriad rydym yn ymddiheuro am hyn; peidiwch os gwelwch yn dda â
> datgelu, anfon ymlaen, printio, copïo na dosbarthu gwybodaeth
> yn yr e-bost
> yma na gweithredu mewn unrhyw fodd drwy ddibynnu ar ei
> gynnwys: gwaherddir
> gwneud hynny'n gyfan gwbl a gallai fod yn anghyfreithlon.
> Rhowch wybod i'r
> anfonwr fod y neges yma wedi mynd ar goll cyn ei dileu.
>
> Mae unrhyw safbwynt neu farn a gyflwynir yn eiddo i'r awdur
> ac nid ydynt o
> anghenraid yn cynrychioli safbwynt neu farn Ymddiriedolaeth
> GIG Gogledd
> Orllewin Cymru.
>
> Gallai cynnwys yr e-bost yma gael ei ddatgelu i'r cyhoedd o
> dan Gôd Bod yn
> Agored y GIG neu Ddeddf Rhyddid Gwybodaeth 2000. Nid oes
> modd gwarantu
> cyfrinachedd y neges ac unrhyw ateb.
>
> Bydd y neges yma ac unrhyw ffeiliau cysylltiedig wedi cael eu
> gwirio gan
> feddalwedd canfod firws cyn eu trosglwyddo. Ond rhaid i'r
> sawl sy'n derbyn
> wirio rhag firws ei hun cyn agor unrhyw ymgysylltiad. Nid yw'r
> Ymddiriedolaeth yn derbyn unrhyw gyfrifoldeb am unrhyw golled
> neu niwed a
> allai gael ei achosi gan firws meddalwedd.
>
>
> This e-mail may contain confidential information and/or
> copyright material.
> If you believe that you have received this e-mail in error
> please accept our
> apologies; please do not disclose, forward, print, copy or distribute
> information in this e-mail or take any action in reliance on
> its contents:
> to do so is strictly prohibited and may be unlawful. Please
> inform the
> sender that this message has gone astray before deleting it.
>
> Any views or opinions presented are to be understood as those
> of the author
> and do not necessarily represent those of the North West
> Wales NHS Trust.
>
> The contents of this e-mail may be subject to public
> disclosure under the
> NHS Code of Openness or the Freedom of Information Act 2000. The
> confidentiality of the message and any reply cannot be guaranteed.
>
> This message and any attached files will have been checked with virus
> detection software before transmission. However, recipients
> must carry out
> their own virus checks before opening any attachment. The
> Trust accepts no
> liability for any loss or damage, which may be caused by
> software viruses.
>
> Gallai'r e-bost yma gynnwys gwybodaeth gyfrinachol a/neu
> ddeunydd hawlfraint. Os ydych chi'n meddwl eich bod wedi
> derbyn yr e-bost yma drwy gamgymeriad rydym yn ymddiheuro am
> hyn; peidiwch os gwelwch yn dda â datgelu, anfon ymlaen,
> printio, copïo na dosbarthu gwybodaeth yn yr e-bost yma na
> gweithredu mewn unrhyw fodd drwy ddibynnu ar ei gynnwys:
> gwaherddir gwneud hynny'n gyfan gwbl a gallai fod yn
> anghyfreithlon. Rhowch wybod i'r anfonwr fod y neges yma wedi
> mynd ar goll cyn ei dileu.
>
> Mae unrhyw safbwynt neu farn a gyflwynir yn eiddo i'r awdur
> ac nid ydynt o anghenraid yn cynrychioli safbwynt neu farn
> Ymddiriedolaeth GIG Gogledd Orllewin Cymru.
>
> Gallai cynnwys yr e-bost yma gael ei ddatgelu i'r cyhoedd o
> dan Gôd Bod yn Agored y GIG neu Ddeddf Rhyddid Gwybodaeth
> 2000. Nid oes modd gwarantu cyfrinachedd y neges ac unrhyw ateb.
>
> Bydd y neges yma ac unrhyw ffeiliau cysylltiedig wedi cael eu
> gwirio gan feddalwedd canfod firws cyn eu trosglwyddo. Ond
> rhaid i'r sawl sy'n derbyn wirio rhag firws ei hun cyn agor
> unrhyw ymgysylltiad. Nid yw'r Ymddiriedolaeth yn derbyn
> unrhyw gyfrifoldeb am unrhyw golled neu niwed a allai gael ei
> achosi gan firws meddalwedd.
>
>
> This e-mail may contain confidential information and/or
> copyright material. If you believe that you have received
> this e-mail in error please accept our apologies; please do
> not disclose, forward, print, copy or distribute information
> in this e-mail or take any action in reliance on its
> contents: to do so is strictly prohibited and may be
> unlawful. Please inform the sender that this message has
> gone astray before deleting it.
>
> Any views or opinions presented are to be understood as those
> of the author and do not necessarily represent those of the
> North West Wales NHS Trust.
>
> The contents of this e-mail may be subject to public
> disclosure under the NHS Code of Openness or the Freedom of
> Information Act 2000. The confidentiality of the message and
> any reply cannot be guaranteed.
>
> This message and any attached files will have been checked
> with virus detection software before transmission. However,
> recipients must carry out their own virus checks before
> opening any attachment. The Trust accepts no liability for
> any loss or damage, which may be caused by software viruses.
>
|