The best I can remember you can't "migrate" into a copypool. However, I would highly recommend, *depending on your environment*, to do these tasks during the day instead. I would assume your clients all do their backups at night, therefore doing these backup processes during the day gives the TSM server a little more time to commit to them.
You can run 1 and 3 simultaneously, and then run 2 giving it all the time it needs. However, there are other solutions. Here are some reasons why the example solution below may not help you: 1. If you do not have any data getting backed up directly to the tapepool, and you have no migration processes that auto kick off during the night/day then I'd wonder why the tapepool -> copypool process is taking so long. 2. In your proposed solution you are not running a backup of the tapepool, and therefore that data will never go offsite. 3. Once you "backup" all the data to a copypool from the VTLpool there would be no reason to "migrate" it to the same location, and as I said above I don't believe you can "migrate" into a copy pool anyway. I guess the main question here is what problem are you trying to solve, and what is happing that's making this an issue? (errors, failed backups, etc.). See Ya' Howard > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Orin Rehorst > Sent: Monday, October 13, 2008 5:20 PM > To: [email protected] > Subject: [ADSM-L] Backup order > > Our TSM was set up to nightly: > > 1. backup the VTLpool to copypool > 2. backup the tapepool to copypool > 3. migrate stg VTLpool (to tapepool) > > Step 2 is tape-to-tape and therefore slow. > > Could I change to eliminate the tape-to-tape and still get the job > done? > > For example: > > 1. backup the VTLpool to copypool > 2. backup the VTLpool to tapepool > 3. migrate stg VTLpool (to copypool) > > > Regards, > Orin > > Orin Rehorst > > * e-mail: [EMAIL PROTECTED] > ( Phone: (713)670-2443 > 7 Fax: (713)670-2457 > > > >
