Shannon, If you have enough disk space you might want to create 2 primary diskpools. One for the O/S data and one for the Domino databases and Transaction Log extents. BTW, are you running Archive Transaction Logging? The logic is based on our scenario:
* We have mail quotas in place for a 50MB mail file and have a 14 day retention. * TDP "Fulls" are run twice a week (script files run Notes compact -B and then domdsmc incremental command afterward) * We archive the Trans Logs every 4 hours and a threshold backup every hour just in case a notes process spikes. We run the Trans Log Archive jobs to a primary diskpool that is big enough to keep 3 days worth of incrementals for expedient restore capability. It migrates to a collocated tape pool. The same tape pool is used for the Domino database backups so that all TDP backups are collocated. The Backup/Archive jobs go to another primary disk pool which is small enough to keep the weekly incrementals from all nodes associated to that TSM server. That data is migrated to a non-collocated tape pool which utilizes the tapes more efficiently because the O/S is a fairly static file system after the first backup and one node would only take up a fraction of one tape. Hope this adds to your understanding! Brian Scott EDS - Enterprise Distributed Capabilities MS 3278 Troy, MI 48098 * phone: 248-265-4596 (8-365) * mailto:[EMAIL PROTECTED] -----Original Message----- From: Shannon Bach [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 16, 2002 12:07 PM To: [EMAIL PROTECTED] Subject: TDP Lotus Domino I am in the process of setting up new Domain, etc. to start using the TDP Lotus Domino for backups. Currently just using the TSM Client for the backups with a primary diskpool big enough for all nightly backups and a primary cartpool(seq,collocated) where I migrate all the backed-up data from disk to before the next nightly backup. Does anyone know if it would be better to create a separate primary storage pool or can I just send the TDP data to the same stgpool we are currently using? Since the seq stgpool is collocated and the TDP gets a different node name than the TSM Notes Client, I'm thinking this shouldn't be a problem, but there may be other issues to take into consideration that I don't know about. From reading all the documentation it seems that all the data from the TDP is considered BACKUP data and not ARCHIVED data. Is this right? Any help to increase my understanding would be greatly appreciated! Shannon Bach Madison Gas & Electric Co. Operations Analyst - Data Center Services Office 608-252-7260 Fax 608-252-7098 e-mail [EMAIL PROTECTED]
