Ok so here are the steps to setup the instance, just remember there will be an outage needed on the current TSM library manager as you remove drives and paths.

The instance starts fast and cycling it for updates or when problems occur keeps downtime to a minimum. When creating our library manager instance I was unsure how large to make the DB so I made it 2GB, and it currently is 4.6% utilized. The key to the dedicated instance is keeping the DB as small as possible and this is easily done if nothing else in run on the instance.

NO BACKUPS OR ARCHIVES SHOULD BE DONE TO THIS INSTANCE. If this instance is on a dedicated server also, do not backup the server to the library manager, back it up to one of the other instances. That’s right, no backups to worry about (except the DB) and even if you lost the systems DB backup and had to start from scratch the other servers sharing this instance could easily reconcile their inventory and you would not lose any server data (so it’s also a lot safer to use than relying on a production TSM instance). Manageability is increased in that all you need to worry about are the drives and their paths. This impact affects library usage and so having the dedicated library manager allows for a smaller DB and no heavy tasks to bog down all the mount requests. Performance wise TSM has DB issues and when large tasks are running all around performance is impacted. There are definite benefits to using a dedicated instance like performance and manageability. I was recently asked how to setup a dedicated TSM Library Manager instance to resolve issues with using a production backup instance as the manager. I had to do this process this weekend as we moved to a new library and library manager and I realized I left out the tape checkin. I had to revise this as I left out the checkin of the tapes before the audit.

How to setup tradeskillmaster