TSM doesn't care whether you leave it there, do MOVE DATA back to TAPEPOOL, or migrate it. If you need to do a restore, TSM knows where the data is, and will go get it.
If it were me, I would move it back (either with MOVE DATA or a migration) so as to 1) have the space available next time and 2) not have to worry about changes to overnight schedules to include backup stgpools, etc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jim Zajkowski Sent: Thursday, January 12, 2006 1:36 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Pre-fetching a restore? On Jan 12, 2006, at 8:18 AM, Allen S. Rout wrote: > I'd say make sure that you pre-stage the data to a different storage > pool than your usual landing pad, if you can possibly find the space. > You could fill up the landing pad, and have it start migration, and be > chasing your tail for quite a bit. Thank you all for the pointer to move nodedata, that does do what I want. My question is a follow-on: Say I have the normal disk storage pool (eg, DISKPOOL) that then migrates to TAPEPOOL. I create a new disk pool named PRESTAGE. I then MOVE NODEDATA from TAPEPOOL to PRESTAGE. That works great. My question is, what should I do after I've either restored the machine or not had to? Should I move the data back to the tapes? Should I set a migration from PRESTAGE back to TAPEPOOL? I see that the tape that had the client's data was reduced by an appropriate amount because of the move. Thanks a bunch, your combined expertise is fantastic! --Jim
