__
Marc Lanteigne
Spectrum Protect Specialist AVP / SRT
-Original Message-
From: Zoltan Forray
Sent: Tuesday, March 12, 2019 10:33 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] best way to avoid long rollback
So you are saying that issuing the server HALT command via console is
t AVP / SRT
> \
>
>
>
> -Original Message-
> From: Zoltan Forray
> Sent: Tuesday, March 12, 2019 10:04 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] best way to avoid long rollback
>
> tsminst1 is a script in /etc/rc.d/init.d which de
_
Marc Lanteigne
Spectrum Protect Specialist AVP / SRT
\
-Original Message-
From: Zoltan Forray
Sent: Tuesday, March 12, 2019 10:04 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] best way to avoid long rollback
tsminst1 is a script in /etc/rc.d/init.d which determines the pid of the
run
ther for Spectrum Protect:
> http://www-01.ibm.com/support/docview.wss?uid=swg22013355
> Spectrum Protect Blueprint: https://ibm.biz/BdHc6b
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
>
> -Original Message-
> From: Zoltan Forray
> Sent: Monday, March 11, 20
edIn
-Original Message-
From: Zoltan Forray
Sent: Monday, March 11, 2019 01:52 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] best way to avoid long rollback
Out of curiosity, why do you do a "systemctl stop tsminst1" (which if I
recall does a kill) vs just HALT the ISP
regards,
Eric van Loon
Air France/KLM Storage & Backup
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of J.
Eric Wonderley
Sent: maandag 11 maart 2019 17:36
To: ADSM-L@VM.MARIST.EDU
Subject: Re: best way to avoid long rollback
We are running rhel7
Out of curiosity, why do you do a "systemctl stop tsminst1" (which if I
recall does a kill) vs just HALT the ISP server immediately after the DB
backup finishes? Our patching takes about the same time (we do it monthly)
since the IBM lin_tape drivers have to be removed before kernel patching
and t
We are running rhel7 on a dell r730 and we just did a full and
dbsnap...ususally take about 1.5h for both to complete.
Typically then shutdown with systemctl stop tsminst1.
I think last time we stopped tsm about an hour after the db finished its
backups. Likely restarted tsm about an hour after
I have to ask what OS/hardware/ISP are you running? What procedure are you
using to prep for the OS patching (we stop client sessions/all admin
processes - do a full DB backup - halt the server)
Our offsite replica server is RHEL 7 on Dell R740xd with 192GB and 3TB SSD
with the DB currently at 2
We have a pair of tsm servers doing backup and replication. Each has a
database over 1TB on ssd and 512G of memory
Our organization likes to do os patch maintenance every 90d and doing this
requires a stop and restart of db2. When would it be best to do
maintenance to shorten the rollback time?
10 matches
Mail list logo
