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 <zfor...@vcu.edu> 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 http://phishing.vcu.edu/ >
