Hello Kumar, well, that's not the way TSM is working. There is no strict correlation between a drive and a node or storagepool. But for your setup, it is still not advisableto backup Database-logs directly to tape because of the latency. Logs are relatively small files, and during the start of a backup the heads of the tape have still to be positioned which will lead to a delay, followed by a small write, followed by a log wait. Rince, lather, repeat. Drives are to expensive for that. So the best setup is to backup big databases to Tape - preferable lanfree, and backup the logs to a diskpool - wich can be drained once an hour (maype earlier) to tape. If you still persist in backing up logs directly to tape, take a look at the mountretention settings in the device-class. Set it to such a value that the tape will not be dismounted between two consecutive log backups and you should be fine.
As for your 2nd wish: TDP for ERP aka SAP-Backup and TDP for Oracle can provide this feature. -- Michael PrixOn Mo, 2016-05-23 at 10:44 +0530, S Kumar wrote: > Hi Maurice, > > Thanks for pointing out at basic level. > > But if you read my mail, where as i have clearly written about the feature > of drive preference in TSM rather than disk pool or any other alternate. > > I am not looking for alternate in my current setup. If i have plenty of > drive in my setup than why will use the disk pool. Also i have the > sufficient SAN Agent license for that. > > > Some where i had read, TSM is fully capable to take the backup in tape, > then why we should not use? > > Draw back of using the disk/file pool is, if disk/file pool and your data > exist in same storage. Suppose if your storage fail or it is not > recoverable, than it is no use. You can'nt restore data from disk pool as > it is in same storage. > > So it is wise to do not use from same storage for backup and data purpose. > > And most of the customer do not have multiple storage. > > Two feature i missing in TSM and i am looking for it and if it is available > its good > > 1. Drive preference for node. > 2. Copy of node data in same TSM Server for safety purpose. Not in replica. > So that we can have two physical media for same node data. > > Regards, > > > > > On Sun, May 22, 2016 at 10:03 PM, Maurice van 't Loo <maur...@backitup.nu> > wrote: > > > Hello Kumar, > > > > Best is to start reading about the TSM basics, or better: do the basic TSM > > training. > > > > In your case I should use a diskpool to receive the archlog data, then > > migrate to tape. In this case you can also use the benefits of > > collocation. > > > > Good luck, > > Maurice > > > > 2016-05-16 12:06 GMT+02:00 S Kumar <our....@gmail.com>: > > > > > Hi, > > > > > > I came to a situation where customer wants database log backup in tape > > > in > > > every two hours. This setup is having more than 10 SAP production server > > > and other database server. So they want logs to be backup of all the > > > production server and other database server in tape. > > > > > > > > > They have plenty of tapes drives, so for him tape drive is not a > > > constraint for them. > > > > > > TSM has been configured with SAN agent and lot of time it is going in > > > mounting and dismounting for various database node. > > > > > > If drive preference is available for a node in TSM then we can define a > > > node for log backup and attached the preferred tape drive with nodes. > > > and > > > these nodes are group to single collocation group. so all the logs > > > backup > > > will go in one drive and single cartridge. So that the cartridge seek > > time > > > can also be avoided. > > > > > > Is there such type of feature is available with TSM. > > > > > > > > > Regards, > > > > >
