ADSM-L

Re: Problem with the Backup! Serious!

2000-05-18 11:07:01
Subject: Re: Problem with the Backup! Serious!
From: "Lambelet,Rene,VEVEY,FC-SIL/INF." <Rene.Lambelet AT NESTLE DOT COM>
Date: Thu, 18 May 2000 17:07:01 +0200
Hello,

ok with you Gary. In addition I would check if there are any waiting tape
mounts as they would hung the adsm server.

I like to do just a stop/start of my Adsm server once a week, during time
where no process and no sessions are running. Just in case...

Regards,



> -----Original Message-----
> From: Gary Ison [SMTP:Gary.Ison AT MAIL.STATE.KY DOT US]
> Sent: Thursday, May 18, 2000 4:58 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Problem with the Backup! Serious!
>
> Robert,
>
>         Did you make any changes to the client options that would have
> increased the backup volume?  Probably not, so were there any network
> problems (or changes)?  The client error logs would be a good place to
> find
> these; the server activity log may also indicate sessions being dropped
> and
> restarted.
>
>         As for the server up time, I don't ever bring it down unless there
> is a general host IPL or a problem with the server itself.  I have run a
> couple of months at a time without restarting the server (I have OS/390
> MVS
> and AIX servers).
>
>         Yes, problems can arise when all these processes are active at the
> same time.  You will get database thrashing and page contention which will
> slow down the server processing in general; sometimes client sessions will
> be terminated due to deadlock situations.  Try to schedule the expiration
> and reclamation on alternate days and outside the client backup windows.
>
>         Another factor that could be in play is long running and intensive
> SQL queries.  They cannot be terminated until their processing is
> completed
> and the also contend for database space and server CPU cycles.  Were any
> of
> these type SQL processes in execution during this time?  The activity log
> should indicate that someone triggered an SQL select, if this is the case.
>
>         Did you experience any database backups during this time?
> Sometimes
> large, uncommitted  transactions will get "hung" in the recovery log and
> cause the database to backup on the automatic trigger.  Look at he vol
> history file for database backup volumes or the server log for backup
> messages.
>
>         Gary L. Ison
>         Governor's Office for Technology
>         101 Cold Harbor Drive
>         Frankfort, Ky.   40601
>         Phone:  (502) 564-8724
>             Fax:  (502) 564-6856
> E-mail: Gary.Ison AT mail.state.ky DOT us <mailto:Gary.Ison AT mail.state.ky 
> DOT us>
>
> -----Original Message-----
> From:   Robert Fijan [SMTP:robert.polensak AT LVA-WUERTTEMBERG DOT DE]
> Sent:   Thursday, May 18, 2000 11:23 AM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        Problem with the Backup! Serious!
>
> Hallo everyvbody outthere.
>
> I got a big problem: until yesterday, our backups went fine and without
> any
> problems. but tonight, they ran around 16 hours per server ( normally
> betwenn 20
> minutes and 4 hours, dependend on the server.)   we have server 3.1.2.50
> on
> OS/390 V2.5,
> Clients are OS/2, NT and AIX ( all V 3.1.2.50 ).
>
> Can anybody imagine, why the backup needs a so long time? Could it be,
> that
> we
> need a IPL every week? normally we do this, but this week we didn't, so
> adsm-server runs for 14 days without stopping/restarting.
>
> Is it a problem, when expiration, reclamation and backup are running the
> same
> time?
>
> Please help me, my boss will kill me when i can't solve the problem.
>
> as a first step i will stop/restart the server now.
>
>
> Please answer soon.
>
>
>
> Greetings and thanks a lot
<Prev in Thread] Current Thread [Next in Thread>