Bill,
As per IBM docs you must have a copy of the volume history file to recover the
server.
But before I threw in the towel I would try to recreate it.
Do you have the disaster recovery file?
If so, open it in notepad and search for VOLUME.HISTORY.FILE
The information contained in that porti
TSM V6.3 on Windows
The volhist file copies were all lost but the .DBS files are still around.
Is there a way to know the backup Series: and Volume Seq: so I can fudge up
a simple volhist with a single BACKUPFULL entry. Or doesn't that matter on a
restore? Or is that information compared to wha
You could always use the "COPY DOMAIN" command to create the new domain, which
would include all current policy sets, management classes, and copy groups.
Then modify as needed.
May be easier than recreating the wheel ..
-Rick Adamson
-Original Message-
From: ADSM: Dist Stor Manage
I don't know that you have to restart the schedules after changing the
node's policy domain, as long as you make sure to reset the schedule
association.
Running QUERY ASSOCIATION when changing the domain is something I always
remember to do the moment after hitting enter.
On Fri, Jun 05, 2015 at
This should work fine. There will be some additional complications if you use
the TSM central scheduler to trigger backups for the affected nodes.
You will need to copy schedule definitions from the old policy domain to the
new one, unless the new one already has suitable schedule definitions.
