Wednesday, November 28, 2012
Tivoli Storage Manager Next Administrative Interface / Beta Programme
The beta test will begin next year. Can IBM make a good Admin GUI for TSM finally? What do you think? I'm still curious!!! ;-)
Thursday, November 15, 2012
STORServer Console 3.0 Released
If you are looking for a TSM management console STORServer has released v3.0 of their console. I have not had the opportunity to use it, but if any reader out their has experience with the product and would like to post a review I will be more than willing to allow it. You can read more about the STORServer Console here.
Tuesday, October 30, 2012
Time For New Phone
My phone contract is up and I want to replace my iPhone 4 with something new. I was going to just replace it with an iPhone 5 but with TSMManager having an Android app for mobile administration I am tempted to move to a Galaxy S III. I have even considered a Galaxy Note 2. I have 3 Android tablets and I am very familiar with ColckworkMod Recovery and playing with different devs. Any suggestions are welcome.
Monday, October 8, 2012
TSM 6.2.4 Binding Issue
We've identified that our TSM 6.2.4 server is not binding files to the default management class but is assigning the node data to the management class with the highest retention setting, as if the default management class was not set. Attempts to update the policy's default management class, reactivate the policy, and rerun a backup have not yielded any rebinding on the TSM side. What does work is placing an INCLUDE * FSMGMT at the top of the include/exclude list. Pretty weird behavior and would explain why we seem to be eating through more storage than we should be. Anyone else seeing this? It might be an isolated incident, but we are checking all our TSM 6.2.x servers to verify. The best way to check is to identify the management class with the largest retention setting for backups and query a nodes backup in that domain to see if it is using it to bind the data.
SELECT * FROM BACKUPS WHERE NODE_NAME='<NAME HERE>' and CLASS_NAME='<MGMT NAME WITH HIGHEST RET IN DOMAIN>'
I have a PMR open with IBM and will post what I find.
SELECT * FROM BACKUPS WHERE NODE_NAME='<NAME HERE>' and CLASS_NAME='<MGMT NAME WITH HIGHEST RET IN DOMAIN>'
I have a PMR open with IBM and will post what I find.
Tuesday, September 4, 2012
Solaris LAN-Free
I recently had to configure a Solaris box for LAN-Free and had to dig up my old documentation. Here's what I did to get LAN-Free to work after loading the drivers and the devices not being found in the tape list file. These directions are for IBM LTO drives only.
http://www-01.ibm.com/support/docvie...S7002972&aid=1
Adobe Reader page 137 (actual doc page 117)
Adobe Reader page 137 (actual doc page 117)
We need to make sure the native "st" driver is not loaded. Run
rem_drv st
to unload. And comment out everything in /kernel/drv/st.conf
then we need to run the following:
rm /dev/rmt/* | removes any tape drive definitions in the rmt folder. Do this only if the IBM tape drives are the only drives used on the server |
/opt/IBMtape/tmd –s | Stops the Tape Monitor Daemon |
/usr/sbin/rem_drv IBMtape | Removes the IBMtape driver |
The commands to reload the device driver are: | |
/usr/sbin/add_drv -m ’* 0666 bin bin’ IBMtape | This reloads the driver but does not set the correct driver type |
/usr/sbin/update_drv -av -i ’"scsiclass,01.vIBM.pULTRIUM-TD3"’ IBMtape | This will add the drive type to the /etc/driver_aliases file. |
/opt/IBMtape/tmd | Reloads the IBM Tape Monitor Daemon |
Then run/opt/IBMtape/tapelist –Ac to see if the drives are discovered correctly.
Wednesday, August 8, 2012
NFS Mount Issue
I recently had a number of AIX server backups miss due to the backup hanging when doing its initial filesystem listing. At some point within the last day the mount's source was rebooted and all the mount points went bad. The problem is that TSM sits there trying to query it even though the default action is to not backup NFS mount points. So I had to log into each server, umount -f the file system, remount it, and then TSM was able to run successfully. TSM does not allow a DOMAIN -ALL-NFS so no matter what I do TSM is going to hang on the listing of file systems. Of course doing a df on the server hangs also, so it's not just a TSM issue. Anyone else ran across this issue?
Subscribe to:
Posts (Atom)