X-ASG-Orig-Subj: Re: basic DR questions
In-Reply-To:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=__PartFBCE68B6.0__="
X-Barracuda-Connect: mail.mrl.ubc.ca[137.82.67.155]
X-Barracuda-Start-Time: 1422572459
X-Barracuda-URL: http://148.100.49.28:8000/cgi-mod/mark.cgi
X-Vir
I've done it just like that in the past (Unix host lost its root disk) it
does work.
On 28 Jan 2015 07:07, "Remco Post" wrote:
> > Op 28 jan. 2015, om 00:25 heeft Andrew Ferris het
> volgende geschreven:
> >
> > Thanks for the reply Rick.
> >
> > Pointing the new TSM server at the old db and log
> Op 28 jan. 2015, om 00:25 heeft Andrew Ferris het
> volgende geschreven:
>
> Thanks for the reply Rick.
>
> Pointing the new TSM server at the old db and log files didn't work so Skylar
> was correct. Got messages saying that they belonged to another TSM server. So
> I will pull back my on
Thanks for the reply Rick.
Pointing the new TSM server at the old db and log files didn't work so Skylar
was correct. Got messages saying that they belonged to another TSM server. So I
will pull back my one DB tape and double check that the server can talk to our
3584/TS3500 and IBM drives.
Andrew,
Been there, done that.
Here's how I handled it:
-Get the server operational. Like others have said it is advantageous to have
several files from the TSM instance directory (volhist, devconfig, and
optionally dsmserv.opt). On 5.x it is possible to recover without them, but the
situation
The database is just find sitting there.
>
> Rick
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Skylar Thompson
> Sent: Tuesday, January 27, 2015 1:03 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: basic DR
Thank you Wanda, Richard, Skylar and Dmitry for your quick responses.
I will try to get the server to use the pre-existing volumes and report back
with what I had to do if it turns out it doesn't work.
Andrew
>>> "Prather, Wanda" 1/27/2015 10:46 AM >>>
Oh yeah,
after you reinstall Windows &
Oh yeah,
after you reinstall Windows & TSM, you'll need to reinstall your tape driver,
whatever that was.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, January 27, 2015 1:41 PM
To: ADSM-L@VM.MARIST.EDU
Subject
Hm. TSM 5.5.
Reinstall Windows
Reinstall TSM
It will create a tiny db and tiny disk pools by default.
Look at the dsmserv.dsk file; it will point to the new DB and log.
I would try doctoring that file to point to the original DB and logs, then
restart TSM and see if it will talk to them. Proba
nager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Skylar
Thompson
Sent: Tuesday, January 27, 2015 1:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: basic DR questions
It sounds like the main thing you'll need is to restore your TSM database.
Having a backup of your volhistory and devconfig files would help
It sounds like the main thing you'll need is to restore your TSM database.
Having a backup of your volhistory and devconfig files would help but if
you have a small site you might be able to do it from memory.
If you are using DISK-type diskpools, you'll want to treat them as
destroyed since volum
DUMPDB - LOADDB - AUDITDB Procedure on a tsm server, which has a corrupt db.
I have never used this procedure but It will help you with corrupted DB
Dmitry Dukhov
Siberia Software SL
http://www.s-iberia.com
On 27/01/15 20:15, Andrew Ferris wrote:
Hello ADSM-ers,
Our ancient 5.5 (EOL I know)
12 matches
Mail list logo
