droach
ADSM.ORG Senior Member
Been playing with a pair of Data Domain (DD) 7200's and am ready to implement with TSM. Having a hard time finding any "best practice" type documentation that contains much detail. Would like to hear from anyone that has TSM and DD running in their world.
We are running TSM on Windows and will NOT be using the DD as a VTL. Will be deploying CIFS shares for TSM device classes as per EMC's recommendation.
Some questions:
Wanted to join the DD controllers to the domain, but all our TSM servers startup under a local account. For testing I just created the same account and pw on the DD and it would allow the TSM servers to connect. Once the DD was joined to the AD domain it would no longer honor these local accounts. Could reconfigure all TSM servers to start using a domain account, but don't like the idea of TSM startup relying on the domain to be available for it to start.
As for the separation of data, don't like the idea of every database server dumping their backups into a single location for RMAN and one for SQL. Seems like you would at least want separate folders in these Storage Units/MTREE for each server to dump into.
Any other "gotcha's" or recommendations are greatly appreciated.
We are running TSM on Windows and will NOT be using the DD as a VTL. Will be deploying CIFS shares for TSM device classes as per EMC's recommendation.
Some questions:
- Did you join your DD controllers to your Active Directory domain?
- For a Primary Data Domain (DD) storage pool...collocate Y/N?, and if so, which method, NODE?
- Reclaim threshold? EMC suggested 90%
- MAXSIze for the device class? 50-100G was suggested
- Separation of data - How did you partition your DD for multiple TSM servers and DDBoost? Was suggested to use a separate MTREE and CIFS share for each TSM server, but define a single Storage Unit/MTREE for DDBoost and RMAN, and a single Storage Unit/MTREE for DDBoost for SQL.
Wanted to join the DD controllers to the domain, but all our TSM servers startup under a local account. For testing I just created the same account and pw on the DD and it would allow the TSM servers to connect. Once the DD was joined to the AD domain it would no longer honor these local accounts. Could reconfigure all TSM servers to start using a domain account, but don't like the idea of TSM startup relying on the domain to be available for it to start.
As for the separation of data, don't like the idea of every database server dumping their backups into a single location for RMAN and one for SQL. Seems like you would at least want separate folders in these Storage Units/MTREE for each server to dump into.
Any other "gotcha's" or recommendations are greatly appreciated.