Joe, you can define a deviceclass with type=file, maxcap=512m. Then you can generate the backupsets to the new deviceclass. The backupset will be written to a one or more dynamically allocated files on your sms managed disks. When the backup set is done you can either FTP the files to the secondary server, our you can FTP them locally to a machine with a cd burner, burn the cd's and mail them.
Since the restore will be done without accessing the server, the name created doesn't have to be preserved, so you can rename the files to bset.f1, bset.f2 etc. to make it easier for the people doing the restore. Hope this helps, ---------- Bill Colwell C. S. Draper Lab Cambridge Ma. At 01:49 PM 2/15/2002 -0500, you wrote: >TSM v413.0 running on os/390 >primarily backing up NT4.0 and ADSMv3.1.06 > >Situation: >We backup branch offices spread thru out the US. Each branch office has a primary >server and an exact duplicate server running the os and the apps (no user data). >Frequently, we will be notified >ahead of time (days) that the primary server needs to be rebuilt. This requires us >to restore the user data upon completion. At times it can be as much as 13G going >across fractional T1 or T3. Due >to the network, this can be a really time consuming restore. > >Question: >Is there a way I can utilize the secondary server as a medium to create Backup Sets >on? >There are no local devices (zip, jazz etc...) at these branch offices. Couldn't use >anyhow because there is no personnel at these branch offices to physically load the >media. Any suggestions as to >how I can use the secondary server to put backupsets on and greatly reduce my restore >time to the primary server? > >Regards, Joe
