Thanks to all for their help. Broke mirror - deleted file from hard disk - recreated volume outside of ADSM - re-mirrored.
All seems well and it has passed the failure page in the DB backup without incident. For reference in the future and out of interest, did I really not need to delete the file itself at the filesystem level and hence save time in its re-creation? Thanks again Stu -----Original Message----- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 11:41 AM To: [EMAIL PROTECTED] Subject: Re: ADSM 3.1 - really need some assistance As I remember the original message, you have one "bad" primary DB volume, and TSM is running on the mirror. I believe the way to "fix" it, is to break the mirror, which you do by deleting the bad volume. ("deleting" just disconnects the volume from TSM, it doesn't physically remove it from the file system.) Then TSM will be running with only one copy of that DB volume. Wait a few minutes, then add the volume back to recreate the mirrored environment. When you re-establish the mirror, TSM will resync the contents by copying the active volume (the original mirror volume) , and both copies will be good when TSM reports they are in sync again. -----Original Message----- From: Ward, Stuart [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 2:30 PM To: [EMAIL PROTECTED] Subject: Re: ADSM 3.1 - really need some assistance Nick Thanks for the response. I have used the 'help' option fairly frequently just recently it seems! It does not, however, indicate any possible solution to correct the page error and there are no other messages or errors relating to the volume in question. I thought that there must be some way of 'fixing' the erroneous copy from the good copy. The database is reported as being 'in sync'. I am stumped right now. Stu -----Original Message----- From: Nicholas Cassimatis [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 1:39 PM To: [EMAIL PROTECTED] Subject: Re: ADSM 3.1 - really need some assistance Stuart, Not to pick on you (not to mention that this could be a fairly complex issue), but did you do a "help anr0207e" on your ADSM server? It indicates to look for other error messages. Look in your actlog for other errors, both at the same timestamp and on the same database volume - F: \ADSM_SERVER\DB\DB5.DSM. Let us know what other errors you're getting, and we may be able to help more. I won't make any guesses from this point, but I do have a feeling of what may have happened. The ADSM/TSM online help is often actually, well, helpful. I'm amazed at how many questions from people I can answer just by looking at the help and following what it says to do. And I'm amazed at how people think I'm so smart when I can find the answers so quickly. Sometimes interpreting what the help screen says takes some doing, but quite often it's pretty plain and simple. Nick Cassimatis [EMAIL PROTECTED] Today is the tomorrow of yesterday.
