JustHall
Active Newcomer
- Joined
- Feb 8, 2010
- Messages
- 6
- Reaction score
- 0
- Points
- 0
Is there a clear, detailed tutorial somewhere on how to install the TSM BA Client on a Windows Server 2008 R2 Ent. x64 failover cluster? Everything we've found is either outdated, not for Server 2008, or impossible for the inexperienced to follow. Even an outline of the entire process start-to-finish would be helpful. We tried to follow the TSM w/ Windows 2008 Clusters presentation, but it didn't give much detail and left us where we are now.
We want to backup the 2 nodes themselves (local disks) as well as the shared storage that may live on either node at any given time. As we understand it, the client acceptor and scheduler need to be associated with that shared storage somehow so that whichever node currently hosts the shared storage will also run the TSM backup. Is that even an accurate understanding of the process?
We tried installing the BA client (web client, client acceptor, and scheduler) on each node. Neither of them can see the shared storage drives. We added a Generic Service to the Windows cluster and pointed it at the TSM Client Acceptor and we can connect to the web client through the cluster network name. We didn't add a second service to the cluster for the scheduler, but we think we may need to - but we're not sure how to tie it to the other services so they all live on the same active node. Not sure where to go from here.
Thanks for any insight.
P.S.
The dsm.opt file on each node is virtually empty, it only contains 2 lines. Is that normal? We expected to see the options we configured during the installation process listed in there, but most of them were default so perhaps it omits those?
TSM BA Client 6.1.3
Windows Server 2008 R2 Enterprise 64-bit
We want to backup the 2 nodes themselves (local disks) as well as the shared storage that may live on either node at any given time. As we understand it, the client acceptor and scheduler need to be associated with that shared storage somehow so that whichever node currently hosts the shared storage will also run the TSM backup. Is that even an accurate understanding of the process?
We tried installing the BA client (web client, client acceptor, and scheduler) on each node. Neither of them can see the shared storage drives. We added a Generic Service to the Windows cluster and pointed it at the TSM Client Acceptor and we can connect to the web client through the cluster network name. We didn't add a second service to the cluster for the scheduler, but we think we may need to - but we're not sure how to tie it to the other services so they all live on the same active node. Not sure where to go from here.
Thanks for any insight.
P.S.
The dsm.opt file on each node is virtually empty, it only contains 2 lines. Is that normal? We expected to see the options we configured during the installation process listed in there, but most of them were default so perhaps it omits those?
TSM BA Client 6.1.3
Windows Server 2008 R2 Enterprise 64-bit