Search:

Actually the system tries to put the ungrouped nodes data together on tape with the nodes previouly saved data, in effect collocating it by node. It is better to have everything grouped when using...

When you set collocation on a storage pool, it affects all the nodes. The nodes in your collocation group will collocate by group within that storage pool. Any nodes not in a collocation group will...

The only thing I found was to upgrade the server to TSM 5.5.2 to correct the issue.

The other thing to remember is that copypool data cannot be moved from one copypool to another like primary pool data. You can't move the data directly from the old copypool to the new copypool.
...

In TSM 5.5, you would have to define a new dbvol and then extend the db to use the new space.

You can look at the admin reference under define dbvol and extend db to get details on the commands....

I would try the TSM Queue, they should be able to point you in the right direction or help you with the problem.

From what I have found, the older clients tend to work with the newer versions of TSM. It is when you try to install a newer client and try to make it work with an older server version that you run...

The only method that I can recall is to uninstall and reinstall the ISC.

Under version 5 you could use something similar to this:

dsmserv restore db volumenames=dsm023,dsm037,dsm087
devclass=tapeclass commit=yes

However, under the manuals for 6.1 and 6.2 I do not...

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp

http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp

Here are the links to the version 5 and 6 manuals. They are a...

Other useful links are:

http://www-947.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager_Extended_Edition
...

Take a look in the admin guide/reference manual, at the move media command, this will give you a idea of how to manage the volumes, you are having to move out of the library in order to maintain...

It is generally not recommended to make that big of a jump, however, I have seen it done several times. Based on my experience, you may have to run the db upgrade command manually in order to start...

You could try doing your incrementals to disk and your fulls to tape. I did all my backups to disk, after a server that I was getting ready to retire lost all its connections to the physical library...

Run a restore volume <vol name> preview=yes. Pull the volumes from offsite it lists in the activity log back onsite and check them back into the library and once they are there, rerun the command...

If the data base is fragmented you may not see a reduction in space, if you want to check for fragmentation try running the "ESTIMATE DBREORGSTATS" command, which can run a very long time and could...

For DRM Query DRMStatus to check number of days your db expiration is set for.

To change the number of days use the SET DRMDBBACKUPEXPIREDAYS Command to set the number of days you want to keep...

You can control the start and end of a schedule window with the duration parameter in the "define schedule" command, it will only allow the job to start within the specified duration.

DURation...

If I remember correctly, you have to delete and redefine the library to TSM so that it will recognize the new frame. I would confirm this with ibm, as it has been awhile since I helped someone do...

You need to make sure their server is the same version as yours or higher, an export/import operation to a lower level server will not work.

When collocation groups is on and there are no groups, it collocates by node, which explains the behavior you were seeing.

The LTO1's do not work with LTO4 tape drives, so you would have to keep an lto1 or lto2 to read and write to them, if you just want to read them then an LTO3 drive would work. The LTO3's can be read...

From the server\bin directory, the same place you start the server in the foreground if the server is not running.
...

Here is a link that goes through versioning and expiration which may help:

http://www-01.ibm.com/support/docview.wss?uid=swg21224145

Your expiration process should be removing files that are...

Since it is a tape you don't need to worry about varying it offline.

The vary command can be found here:
...

Here is a link to a tech doc, that will walk you through the process.

http://www-01.ibm.com/support/docview.wss?uid=swg21219227

Are the tapes still in the library? If so, then update them to readwrite and retry reclamation. Monitor them to see if they go back to unavailable or not, if they do, then search the activity log...

What are you seeing in the activity log when the tapes go into the unavailable state?

If you are using disaster recovery manager (DRM) it controls the expiration of your db volumes. Using a delete volh to do your db volumes in addition to it, will cause you to lose track of the...

I talked to a friend, here is a copy of the steps:

The following procedures need to be run in order to completely remove the TSM client/server software:

Stop all TSM services that may be...

Search the activity log, is the volume throwing errors?

If it doesn't show update it available and see what happens:

upd vol <vol_name> acc=readw

If the volume continues to throw errors...

Type=remote is an undocumented option and does work. I have used it a number of times and it has appeared in apars and techdocs from IBM.

Since the volumes are tracked via volhist as remote volumes you may have to do the following on each volume, then either label them back in or check them back in.

DEL VOLHIST TODATE=TODAY...

Use the search box, type in "interview" this should allow you to find various questions that have been posted previously in the forums. However, real world experience with TSM really helps when it...

If tape2 is in the copypool, the fix is to delete the volume and do a backup stgpool to rebuild the volume. Once complete, you should be able to restore the volume in the primary pool.

That is...

I talked to a friend, here is a copy of the steps:

The following procedures need to be run in order to completely remove the TSM client/server software:

Stop all TSM services that may be...

I should have tested it before I posted it, it worked last week.

Just in case, you can't remove the client smoothly, here is a link to an IBM document that explains how to remove it manually:


http://www-01.ibm.com/support/docview.wss?uid=swg21141048

I...

TSM will mount tapes, two per reclamation process as it has to read the data from one tape to put in on the other.

For the tapes you have no listing for, try running a checkin libv with the...

Cool, progress, finally.

Is the drive showing any error codes, flashing yellow in the library?

all volumes by node name with archive data

select volume_name from contents where type='Arch' and node_name='ANIL'

all volumes by node name with backup data

select volume_name from...

You cannot move data directly from one copypool to another. You would have to backup the data from the primary pool into the newly created LTO4 pool. Then delete the lto2 volumes in the copypool...

LTO4 drives?

http://www-01.ibm.com/support/docview.wss?uid=swg21269649

http://www-01.ibm.com/support/docview.wss?uid=swg21294024

Search IBM website for either post db restore or 1294024