Re: MSSQL retention for deleted databases
Thanks Skylar. I noticed it was possible to inactive by running "tdpsqlc inactivate " but the problem from our TSM side is that we don't notice these things and doing regular investigations into this matter is a chore. Wondered if there could be some settings or other tricks to automate this. Regards, Hans Chr. On Tue, Mar 12, 2019 at 4:17 PM Skylar Thompson wrote: > A few ways to do it: > > 1. Run a full incremental backup on the node after the database is removed > 2. Use the client-side EXPIRE command with a list of paths to mark inactive > 3. If the entire node is going away, use the server-side DECOMMISSION NODE > command (take note of the caveats in the documentation though) > > On Tue, Mar 12, 2019 at 04:08:58PM +0100, Hans Christian Riksheim wrote: > > Newbie question(only 18 years of experience with TSM) : > > > > How do I ensure that deleted databases get inactivated and expired > > according to the copygroup settings? As far as I know inactivation of > > copies >retonly occurs when the database is backed up. If the database is > > removed all active copies will stay active forever and it is now a manual > > task to inactivate them from the client. > > > > Regards, > > > > Hans Chr. > > -- > -- Skylar Thompson (skyl...@u.washington.edu) > -- Genome Sciences Department, System Administrator > -- Foege Building S046, (206)-685-7354 > -- University of Washington School of Medicine >
Re: MSSQL retention for deleted databases
A few ways to do it: 1. Run a full incremental backup on the node after the database is removed 2. Use the client-side EXPIRE command with a list of paths to mark inactive 3. If the entire node is going away, use the server-side DECOMMISSION NODE command (take note of the caveats in the documentation though) On Tue, Mar 12, 2019 at 04:08:58PM +0100, Hans Christian Riksheim wrote: > Newbie question(only 18 years of experience with TSM) : > > How do I ensure that deleted databases get inactivated and expired > according to the copygroup settings? As far as I know inactivation of > copies >retonly occurs when the database is backed up. If the database is > removed all active copies will stay active forever and it is now a manual > task to inactivate them from the client. > > Regards, > > Hans Chr. -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
MSSQL retention for deleted databases
Newbie question(only 18 years of experience with TSM) : How do I ensure that deleted databases get inactivated and expired according to the copygroup settings? As far as I know inactivation of copies >retonly occurs when the database is backed up. If the database is removed all active copies will stay active forever and it is now a manual task to inactivate them from the client. Regards, Hans Chr.
Docker excludes
Hi All, Is there a way to exclude docker filesystems? I.e. is it possible to useva wildcard in exclude.fs? Richard.
SQL backup excludedb limitation
I have a database backup where the DBA just excluded 100 databases (out of 171). To prevent backup "failures" (and trouble tickets) I tried to exclude them in the command line, but there were 3500 characters just in the excludes. Windows server 2012R2 can handle over 8000 characters in the command line but apparently TSM TDP SQL backup cannot as the long tdpsqlc command produced no output. I could not find any way to reference a file with a list of exclusions, and I'm not sure if the OPT file would work either? Maybe if I list each DB on a separate line in the OPT file?
Re: best way to avoid long rollback
It depends on the signal you use. A standalone "kill" or a "kill -15"
yes. That's called SIGTERM, all it does is send a termination signal to
the process.
https://major.io/2010/03/18/sigterm-vs-sigkill/
-
Thanks,
Marc...
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 no
different than the OS level kill?
On Tue, Mar 12, 2019 at 9:15 AM Marc Lanteigne
wrote:
> That's what I said.
>
> > From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> > command, but without any signal, which means it defaults to -15
> > (SIGTERM). That sends a message to the process to shutdown gracefully.
>
> It's in the manual as one of the proper ways to start/stop the server:
>
> https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t
> _srv_startsrv_autolnx-linux.html
>
>
> If the wrapper was doing a "kill -9", that would be a completely
> different ball of wax.
>
> -
> Thanks,
> Marc...
>
> 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
> running dsmserv process and then issues a kill against it. From the
> tsminst1 script
>
> stop() {
> echo "Stopping $prog instance $instance ..."
> if [[ -e $pidfile ]]
> then
># make sure someone else didn't kill us already
>progpid=`cat $pidfile`
>running=`ps -ef | grep $prog | grep -w $progpid | grep -v
grep`
>if [[ -n $running ]]
>then
> #echo "executing cmd kill `cat $pidfile`"
> * kill `cat $pidfile`*
>
> total_slept=0
> while check_running; do \
> echo "$prog instance $instance still running, will
> check after $SLEEP_INTERVAL seconds"
> sleep $SLEEP_INTERVAL
> total_slept=`expr $total_slept + 1`
>
>
> On Tue, Mar 12, 2019 at 7:57 AM Marc Lanteigne
>
> wrote:
>
> > "systemctl stop tsminst1" is not a kill. That's a service command to
> tell
> > the application it manages to shut down gracefully.
> >
> > From the KC:
> >
> > https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install
> > /t
> > _srv_startsrv_autolnx-linux.html
> >
> > 6.To start or stop the server, issue one of the following commands:
> > To start the server:
> > service tsminst1 start
> >
> > To stop the server:
> > service tsminst1 stop
> >
> > From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> > command, but without any signal, which means it defaults to -15
> > (SIGTERM). That sends a message to the process to shutdown gracefully.
> >
> > -
> > Thanks,
> > Marc...
> >
> > Marc Lanteigne
> > Spectrum Protect Specialist AVP / SRT
> > 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to
> > Friday, 7:00 to 16:00 Eastern
> >
> > Latest Servermon for Spectrum Protect:
> > http://www-01.ibm.com/support/docview.wss?uid=swg21432937
> > Performance Mustgather for Spectrum Protect:
> > http://www-01.ibm.com/support/docview.wss?uid=swg22013355
> > Spectrum Protect Blueprint:
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__ibm.biz_BdHc6b;
> > d=
> > DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9P
> > JB
> > RSlL8Q4=PfoOhf0AogsmsP_PMpFEYMv80kMhcTVxSF76MpF_hsk=LwtR0_gcb0BG
> > 2-
> > HKfoR-2RTOuld1nkMKkRqYJJzzdNg=
> >
> > Follow me on: Twitter, developerWorks, LinkedIn
> >
> >
> >
> > -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 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 then reinstalled afterwards which
adds to the time.
> >
> > On Mon, Mar 11, 2019 at 12:38 PM J. Eric Wonderley
> >
> > wrote:
> >
> > > 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
Re: best way to avoid long rollback
So you are saying that issuing the server HALT command via console is no
different than the OS level kill?
On Tue, Mar 12, 2019 at 9:15 AM Marc Lanteigne
wrote:
> That's what I said.
>
> > From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> > command, but without any signal, which means it defaults to -15
> > (SIGTERM). That sends a message to the process to shutdown gracefully.
>
> It's in the manual as one of the proper ways to start/stop the server:
>
> https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t_srv_startsrv_autolnx-linux.html
>
>
> If the wrapper was doing a "kill -9", that would be a completely different
> ball of wax.
>
> -
> Thanks,
> Marc...
>
> 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
> running dsmserv process and then issues a kill against it. From the
> tsminst1 script
>
> stop() {
> echo "Stopping $prog instance $instance ..."
> if [[ -e $pidfile ]]
> then
># make sure someone else didn't kill us already
>progpid=`cat $pidfile`
>running=`ps -ef | grep $prog | grep -w $progpid | grep -v grep`
>if [[ -n $running ]]
>then
> #echo "executing cmd kill `cat $pidfile`"
> * kill `cat $pidfile`*
>
> total_slept=0
> while check_running; do \
> echo "$prog instance $instance still running, will check
> after $SLEEP_INTERVAL seconds"
> sleep $SLEEP_INTERVAL
> total_slept=`expr $total_slept + 1`
>
>
> On Tue, Mar 12, 2019 at 7:57 AM Marc Lanteigne
> wrote:
>
> > "systemctl stop tsminst1" is not a kill. That's a service command to
> tell
> > the application it manages to shut down gracefully.
> >
> > From the KC:
> >
> > https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t
> > _srv_startsrv_autolnx-linux.html
> >
> > 6.To start or stop the server, issue one of the following commands:
> > To start the server:
> > service tsminst1 start
> >
> > To stop the server:
> > service tsminst1 stop
> >
> > From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> > command, but without any signal, which means it defaults to -15
> > (SIGTERM). That sends a message to the process to shutdown gracefully.
> >
> > -
> > Thanks,
> > Marc...
> >
> > Marc Lanteigne
> > Spectrum Protect Specialist AVP / SRT
> > 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to
> > Friday, 7:00 to 16:00 Eastern
> >
> > Latest Servermon for Spectrum Protect:
> > http://www-01.ibm.com/support/docview.wss?uid=swg21432937
> > Performance Mustgather for Spectrum Protect:
> > http://www-01.ibm.com/support/docview.wss?uid=swg22013355
> > Spectrum Protect Blueprint:
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__ibm.biz_BdHc6b=
> > DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJB
> > RSlL8Q4=PfoOhf0AogsmsP_PMpFEYMv80kMhcTVxSF76MpF_hsk=LwtR0_gcb0BG2-
> > HKfoR-2RTOuld1nkMKkRqYJJzzdNg=
> >
> > Follow me on: Twitter, developerWorks, LinkedIn
> >
> >
> >
> > -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 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 then reinstalled afterwards which adds to the time.
> >
> > On Mon, Mar 11, 2019 at 12:38 PM J. Eric Wonderley
> >
> > wrote:
> >
> > > 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 tsm stopped.
> > > It takes roughly and an hour for us to do all of the patching
> > > tripwire reboot etc that we do.
> > >
> > > On Mon, Mar 11, 2019 at 12:19 PM Zoltan Forray
> wrote:
> > >
> > > > 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
Re: best way to avoid long rollback
That's what I said.
> From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> command, but without any signal, which means it defaults to -15
> (SIGTERM). That sends a message to the process to shutdown gracefully.
It's in the manual as one of the proper ways to start/stop the server:
https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t_srv_startsrv_autolnx-linux.html
If the wrapper was doing a "kill -9", that would be a completely different
ball of wax.
-
Thanks,
Marc...
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
running dsmserv process and then issues a kill against it. From the
tsminst1 script
stop() {
echo "Stopping $prog instance $instance ..."
if [[ -e $pidfile ]]
then
# make sure someone else didn't kill us already
progpid=`cat $pidfile`
running=`ps -ef | grep $prog | grep -w $progpid | grep -v grep`
if [[ -n $running ]]
then
#echo "executing cmd kill `cat $pidfile`"
* kill `cat $pidfile`*
total_slept=0
while check_running; do \
echo "$prog instance $instance still running, will check
after $SLEEP_INTERVAL seconds"
sleep $SLEEP_INTERVAL
total_slept=`expr $total_slept + 1`
On Tue, Mar 12, 2019 at 7:57 AM Marc Lanteigne
wrote:
> "systemctl stop tsminst1" is not a kill. That's a service command to
tell
> the application it manages to shut down gracefully.
>
> From the KC:
>
> https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t
> _srv_startsrv_autolnx-linux.html
>
> 6.To start or stop the server, issue one of the following commands:
> To start the server:
> service tsminst1 start
>
> To stop the server:
> service tsminst1 stop
>
> From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> command, but without any signal, which means it defaults to -15
> (SIGTERM). That sends a message to the process to shutdown gracefully.
>
> -
> Thanks,
> Marc...
>
> Marc Lanteigne
> Spectrum Protect Specialist AVP / SRT
> 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to
> Friday, 7:00 to 16:00 Eastern
>
> Latest Servermon for Spectrum Protect:
> http://www-01.ibm.com/support/docview.wss?uid=swg21432937
> Performance Mustgather for Spectrum Protect:
> http://www-01.ibm.com/support/docview.wss?uid=swg22013355
> Spectrum Protect Blueprint:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__ibm.biz_BdHc6b=
> DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJB
> RSlL8Q4=PfoOhf0AogsmsP_PMpFEYMv80kMhcTVxSF76MpF_hsk=LwtR0_gcb0BG2-
> HKfoR-2RTOuld1nkMKkRqYJJzzdNg=
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
>
> -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 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 then reinstalled afterwards which adds to the time.
>
> On Mon, Mar 11, 2019 at 12:38 PM J. Eric Wonderley
>
> wrote:
>
> > 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 tsm stopped.
> > It takes roughly and an hour for us to do all of the patching
> > tripwire reboot etc that we do.
> >
> > On Mon, Mar 11, 2019 at 12:19 PM Zoltan Forray wrote:
> >
> > > 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.3TB used. We patch monthly and never
> > > had it take more than 15-minutes from OS reboot to ISP server
> > > being
> available!
> > >
> > > On Mon, Mar 11, 2019 at 11:41 AM J. Eric Wonderley <
> > eric.wonder...@vt.edu>
> > > wrote:
> > >
> > > > We have a pair of tsm servers doing backup and replication.
> > > > Each has a database over 1TB on ssd and 512G of
Re: best way to avoid long rollback
tsminst1 is a script in /etc/rc.d/init.d which determines the pid of the
running dsmserv process and then issues a kill against it. From the
tsminst1 script
stop() {
echo "Stopping $prog instance $instance ..."
if [[ -e $pidfile ]]
then
# make sure someone else didn't kill us already
progpid=`cat $pidfile`
running=`ps -ef | grep $prog | grep -w $progpid | grep -v grep`
if [[ -n $running ]]
then
#echo "executing cmd kill `cat $pidfile`"
* kill `cat $pidfile`*
total_slept=0
while check_running; do \
echo "$prog instance $instance still running, will check
after $SLEEP_INTERVAL seconds"
sleep $SLEEP_INTERVAL
total_slept=`expr $total_slept + 1`
On Tue, Mar 12, 2019 at 7:57 AM Marc Lanteigne
wrote:
> "systemctl stop tsminst1" is not a kill. That's a service command to tell
> the application it manages to shut down gracefully.
>
> From the KC:
>
> https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t_srv_startsrv_autolnx-linux.html
>
> 6.To start or stop the server, issue one of the following commands:
> To start the server:
> service tsminst1 start
>
> To stop the server:
> service tsminst1 stop
>
> From the /etc/init.d/tsminst1 wrapper script, it does do a kill command,
> but without any signal, which means it defaults to -15 (SIGTERM). That
> sends a message to the process to shutdown gracefully.
>
> -
> Thanks,
> Marc...
>
> Marc Lanteigne
> Spectrum Protect Specialist AVP / SRT
> 416.478.0233 | marclantei...@ca.ibm.com
> Office Hours: Monday to Friday, 7:00 to 16:00 Eastern
>
> Latest Servermon for Spectrum Protect:
> http://www-01.ibm.com/support/docview.wss?uid=swg21432937
> Performance Mustgather 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, 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 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 then reinstalled afterwards which adds to the time.
>
> On Mon, Mar 11, 2019 at 12:38 PM J. Eric Wonderley
> wrote:
>
> > 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 tsm stopped.
> > It takes roughly and an hour for us to do all of the patching tripwire
> > reboot etc that we do.
> >
> > On Mon, Mar 11, 2019 at 12:19 PM Zoltan Forray wrote:
> >
> > > 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.3TB used. We patch monthly and never had
> > > it take more than 15-minutes from OS reboot to ISP server being
> available!
> > >
> > > On Mon, Mar 11, 2019 at 11:41 AM J. Eric Wonderley <
> > eric.wonder...@vt.edu>
> > > wrote:
> > >
> > > > 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?
> > > >
> > > > I would think after completing the db backups. Last time we did
> > > > maintenance about 1h after backups completed it took >2h for the
> > > > db to
> > > come
> > > > up.
> > > >
> > > > Thanks
> > > >
> > >
> > >
> > > --
> > > *Zoltan Forray*
> > > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> > > Xymon Monitor Administrator VMware Administrator Virginia
> > > Commonwealth University UCC/Office of Technology Services
> > > www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing
> > > victim - VCU and other reputable organizations will never use email
> > > to request that you reply with your password, social security number
> > > or confidential personal information. For more details visit
> > >
Re: best way to avoid long rollback
"systemctl stop tsminst1" is not a kill. That's a service command to tell the application it manages to shut down gracefully. >From the KC: https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t_srv_startsrv_autolnx-linux.html 6.To start or stop the server, issue one of the following commands: To start the server: service tsminst1 start To stop the server: service tsminst1 stop >From the /etc/init.d/tsminst1 wrapper script, it does do a kill command, but without any signal, which means it defaults to -15 (SIGTERM). That sends a message to the process to shutdown gracefully. - Thanks, Marc... Marc Lanteigne Spectrum Protect Specialist AVP / SRT 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to Friday, 7:00 to 16:00 Eastern Latest Servermon for Spectrum Protect: http://www-01.ibm.com/support/docview.wss?uid=swg21432937 Performance Mustgather 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, 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 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 then reinstalled afterwards which adds to the time. On Mon, Mar 11, 2019 at 12:38 PM J. Eric Wonderley wrote: > 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 tsm stopped. > It takes roughly and an hour for us to do all of the patching tripwire > reboot etc that we do. > > On Mon, Mar 11, 2019 at 12:19 PM Zoltan Forray wrote: > > > 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.3TB used. We patch monthly and never had > > it take more than 15-minutes from OS reboot to ISP server being available! > > > > On Mon, Mar 11, 2019 at 11:41 AM J. Eric Wonderley < > eric.wonder...@vt.edu> > > wrote: > > > > > 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? > > > > > > I would think after completing the db backups. Last time we did > > > maintenance about 1h after backups completed it took >2h for the > > > db to > > come > > > up. > > > > > > Thanks > > > > > > > > > -- > > *Zoltan Forray* > > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > > Xymon Monitor Administrator VMware Administrator Virginia > > Commonwealth University UCC/Office of Technology Services > > www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing > > victim - VCU and other reputable organizations will never use email > > to request that you reply with your password, social security number > > or confidential personal information. For more details visit > > https://urldefense.proofpoint.com/v2/url?u=http-3A__phishing.vcu.edu > > _=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCG > > Sh9PJBRSlL8Q4=F_EEf1krKkfXHfk6n1Ly1R4pJGcAd7jIzS0Gsls-pbM=nAATGI > > _Luo77W-RZpuAQ8uLoaF0ODjnjGZX4Li4bSE8= > > > -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit https://urldefense.proofpoint.com/v2/url?u=http-3A__phishing.vcu.edu_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4=F_EEf1krKkfXHfk6n1Ly1R4pJGcAd7jIzS0Gsls-pbM=nAATGI_Luo77W-RZpuAQ8uLoaF0ODjnjGZX4Li4bSE8=
Re: best way to avoid long rollback
Hi Eric, Just like Zoltan said, you really need to prevent a kill of TSM. This will leave the DB2 database in an inconsistent state and thus result in a DB2 crash recovery which can indeed be a lengthy process. Just use a halt to stop TSM and the DB2 database will be closed properly. Kind 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 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 tsm stopped. It takes roughly and an hour for us to do all of the patching tripwire reboot etc that we do. On Mon, Mar 11, 2019 at 12:19 PM Zoltan Forray wrote: > 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.3TB used. We patch monthly and never > had it take more than 15-minutes from OS reboot to ISP server being available! > > On Mon, Mar 11, 2019 at 11:41 AM J. Eric Wonderley > > wrote: > > > 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? > > > > I would think after completing the db backups. Last time we did > > maintenance about 1h after backups completed it took >2h for the db > > to > come > > up. > > > > Thanks > > > > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon > Monitor Administrator VMware Administrator Virginia Commonwealth > University UCC/Office of Technology Services www.ucc.vcu.edu > zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and > other reputable organizations will never use email to request that you > reply with your password, social security number or confidential > personal information. For more details visit http://phishing.vcu.edu/ > For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
