As long as there is a copy of every file in (at least) one primary
storage pool, and a copy of the same file on any copy storage pool,
you're in good shape. It doesn't matter which pools, because your
database tracks where it is.
 
--
Mark Stapleton (mark.stapleton AT cdw DOT com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Minns, Farren - Chichester
> Sent: Thursday, November 20, 2008 6:55 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Old copypool data question
> 
> Thanks Rainer
> 
> But I'm wondering if I'm still in a position to do that.
> 
> Here's what we did. Rename our original tapepool and copypool to
> tapepool_3590 and copypool_3590.
> 
> Then created new tapepool and copypool with device class of 3592.
> 
> I then went through the long process of moving data from the
> tapepool_3590 volumes to tapepool volumes (now using 3592 media), one
> tape at a time. This has all been done.
> 
> So now I have all the old on-site primary pool 3590 data on 3592
media,
> and all offsite data being written to 3592 as well.
> 
> Will this have taken into account the old 3590 offsite copypool_3590
> media?
> 
> From a DRM point of view those tapes are still required in the event
of
> a disaster.
> 
> Thanks again
> 
> Farren
> 
> 
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Rainer Wolf
> Sent: 20 November 2008 11:42
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Old copypool data question
> 
>  y.com>
> In-Reply-To: <40F507919CB02E4AA5A48A4F2517A5E810276D2C9B@CHI-
> MB.wiley.com>
> Content-Type: text/plain; charset=us-ascii; format=flowed
> Content-Transfer-Encoding: 7bit
> X-Virus-Scanned: by amavisd-new
> X-Barracuda-Connect: mail.uni-ulm.de[134.60.1.11]
> X-Barracuda-Start-Time: 1227181339
> X-Barracuda-Encrypted: AES256-SHA
> X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210
> X-Barracuda-Virus-Scanned: by Email Relay at marist.edu
> X-Barracuda-Spam-Score: -2.02
> X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of
> TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=
> X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.10699
>         Rule breakdown below
>          pts rule name              description
>         ---- ----------------------
-----------------------------------
> ---------------
> 
> Hi,
> first step:
>      backup stg primary-pool new-copy-pool
> If any data in this first step may not be readable from the
primary-stg
> you still can restore that data from the old copy-pool,
> so be sure that the first step has finished without failures
> 
> and then second step:
>    delete the old copy-storagepool-volumes with craeting and executing
> a macro del.mac
>   consisting of  lines like
>   'del vol xxx discardd=yes wait=yes'
>   ... for every volume in that old copy-pool
>   you easily start that macro from a dsmadmc-shell using the '-
> itemcommit' option
>   as  'macro del.mac'
> 
> regards
> Rainer
> 
> 
> Minns, Farren - Chichester schrieb:
> 
> > Hi All
> >
> > A few months ago I renamed our old copypool and created a new one
> with a new device class to make use of our 3592 tape drives.
> >
> > So I now have lots of 3590 copypool volumes with data on them, and I
> want to move them to the new 3592 media.
> >
> > What is the best way to do this?
> >
> > Many thanks in advance
> >
> > Farren Minns
> > John Wiley & Sons Ltd
> >
---------------------------------------------------------------------
> ---------------------------------------
> > This email (and any attachment) is confidential, may be legally
> privileged and is intended solely for the
> > use of the individual or entity to whom it is addressed. If you are
> not the intended recipient please do
> > not disclose, copy or take any action in reliance on it. If you have
> received this message in error please
> > tell us by reply and delete all copies on your system.
> >
> > Although this email has been scanned for viruses you should rely on
> your own virus check as the sender
> > accepts no liability for any damage arising out of any bug or virus
> infection. Please note that email
> > traffic data may be monitored and that emails may be viewed for
> security reasons.
> >
> > John Wiley & Sons Limited is a private limited company registered in
> England with registered number 641132.
> >
> > Registered office address: The Atrium, Southern Gate, Chichester,
> West Sussex, PO19 8SQ.
> >
---------------------------------------------------------------------
> ---------------------------------------
> 
> --
>
-----------------------------------------------------------------------
> -
> Rainer Wolf                          eMail:       rainer.wolf@uni-
> ulm.de
> kiz - Abt. Infrastruktur           Tel/Fax:      ++49 731 50-
> 22482/22471
> Universitaet Ulm                     wwweb:        http://kiz.uni-
> ulm.de
>
-----------------------------------------------------------------------
> -------------------------------------
> This email (and any attachment) is confidential, may be legally
> privileged and is intended solely for the
> use of the individual or entity to whom it is addressed. If you are
not
> the intended recipient please do
> not disclose, copy or take any action in reliance on it. If you have
> received this message in error please
> tell us by reply and delete all copies on your system.
> 
> Although this email has been scanned for viruses you should rely on
> your own virus check as the sender
> accepts no liability for any damage arising out of any bug or virus
> infection. Please note that email
> traffic data may be monitored and that emails may be viewed for
> security reasons.
> 
> John Wiley & Sons Limited is a private limited company registered in
> England with registered number 641132.
> 
> Registered office address: The Atrium, Southern Gate, Chichester, West
> Sussex, PO19 8SQ.
>
-----------------------------------------------------------------------
> -------------------------------------