TSM Web admin GUI on server 5.5 / 5.4

Since TSM (IBM Backup Solution) version 5.3, the old web Admin GUI has been replaced by a servlet called the ISC console. Now, generally everyone dislikes ISC, cause it’s slow, and uses quite some resources. One can, however, restore the old admin GUI in 5.3 :

IBM has made the old gui available for download. The site contains an installation procedure as well.

It really works w/ 5.4 server and used to work very well on 5.5 at my previous site.

Add volumes to TSM server primary storagepool -disk storage volume

Our TSM server is hosted on AIX 5.3 attached to fastT and ESS shark.

Add LUN from SAN. Our TSM server is attached to fastT as well as ESS shark. In this example I’ve already created a 500 gb LUN from fastT and assigned to tsm server. (some other time I’ll blog about how to assign lun to host)

Anyway here we are …

#fget_config -Av
hdisk73 dac1 2 tsmpool_tsm640

Within than LUN, create a VG and create lv and file system. I’ve created five LVs- file systems on AIX server which servers as our TSM server
#lsvg -l poolvg
poolvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
loglv02 jfs2log 1 1 1 open/syncd N/A
fslv05 jfs2 3040 3040 1 open/syncd /tsm/pool01
fslv06 jfs2 3040 3040 1 open/syncd /tsm/pool02
fslv07 jfs2 3040 3040 1 open/syncd /tsm/pool03
fslv08 jfs2 3040 3040 1 open/syncd /tsm/pool04
fslv09 jfs2 3040 3040 1 open/syncd /tsm/pool05

With TSM 5.5, I still like to use old TSM console, so within TSM server console go to Object view–> Server Storage –> define disk storage volume –> Enter following details

Storage Pool Name: The name of the storage pool to which the volume will be assigned is displayed.
Volume Name: Enter the name of the storage pool volume. This name is required. The name is dependent on the operating system.

I created 10 volumes within each file system of approx 10 gig each w/ name /tsm/pool01/disk01 – /tsm/pool01/disk10 repeated same thing for other file systems.

Note that Formatting the volumes take some time as it is done as an internal TSM activity. You can see these volumes thru AIX cmd line as well –

# cd /tsm/pool01
# ls
disk01 disk03 disk05 disk07 disk09
disk02 disk04 disk06 disk08 lost+found

DONT FORGET TO ADD THESE FILES TO EXCLUDE list in dsm.sys if you back your tsm server itself.

exclude.fs /tsm/pool01
exclude.fs /tsm/pool02
exclude.fs /tsm/pool03
exclude.fs /tsm/pool04
exclude.fs /tsm/pool05

TSM Point in time restore

When performing a point-in-time restore, consider the following:

• Tivoli Storage Manager restores file versions from the most recent backup before the specified point-in-time date. Ensure the point-in-time that you specify is not the same as the date and time this backup was performed.
• If the date and time you specify for the object you are trying to restore is earlier than the oldest version that exists on the server, Tivoli Storage Manager cannot restore that object.
• Point-in-time restore will restore files deleted from the client workstation after the point-in-time date but not files deleted before this date.
• Tivoli Storage Manager cannot restore a file created after the point-in-time date and time. When a point-in-time restore runs, files that were created on the client after the point-in-time date are not deleted.

If there are no backup versions of a directory for the point-in-time you specify, files within that directory are not restorable from the GUI. However, you can restore these files from the command line.

You can start point-in-time restore from the command-line client using the pitdate and pittime options with the query backup and restore commands. For example, when you use the pitdate and pittime options with the query backup command, you establish the point-in-time for which file information is returned. When you use pitdate and pittime with the restore command, the date and time values you specify establish the point-in-time for which files are returned. If you specify pitdate without a pittime value, pittime defaults to 23:59:59. If you specify pittime without a pitdate value, it is ignored.