Tivoli LDAP

We are relatively new to Tivoli LDAP and I see that there are some maintenance and optimization tasks. Just wondering what other Lawson clients do on a regular basis to maintain Tivoli.

Find more posts tagged with

Comments

todd-brown

We do a weekly backup of the db2 instance. That requires db2 to be shutdown. I will be interested to see what others say in this thread as well. Infor is not any help with this topic.

Wichtige Lösungen in der Wissensdatenbank Mai 2012.pdf

Legacy Contributor

We do a weekly process also. Stop DB , back up DB, restart DB

martin-doherty

We stop and backup ours every night. Have had no problems with it.

todd-brown

Are you all doing an idsdbback or just gettng the db owners files.

martin-doherty

Tivoli is on our Lawson server and we are just backing up all files.

Legacy Contributor

Is anyone familiar with doing a "Hot backup" of Tivoli? Can you share some knowledge if so?

Legacy Contributor

I've been doing the backup manually using the admin tool. Can someone share the command line method? Does anyone run the database optimize or maintenance (index reorg) options?

jacob-jellison

Here is snippet of code....not written by me:

cd /lawson/backup/ldap
# Save the last backup set
DATE=`date +%Y%m%d%H%M`
SAVE_DIR=`echo "ldap_"${DATE}`
mkdir $SAVE_DIR
mv BACKUP_FILES/dbback.dat BACKUP_FILES/ibms* BACKUP_FILES/schema* $SAVE_DIR
# run the backup
idsdbback -q -I db2inst1 -k /lawson/backup/ldap
# Stop DB2
db2stop

I have yet had a need to try and restore tds data from backup.....knock on wood!

Legacy Contributor

So you're saying this will execute the online backup? Cool...

Legacy Contributor

a good backup is a BAD backup if not tested.

Legacy Contributor

Weekly: backup TDS using backup routine from J. David Schronce's tds.sh script. It basically does:

TIVOLI_HOME=/opt/IBM/ldap/V6.1
INSTNAMES="idsinst "
BACKUPDIR=/opt/IBM/ldap/backup/dbback
DTSTAMP=`date '+%Y%m%d%H%M%S'`
mkdir -p $BACKUPDIR/$INSTANCE.$DTSTAMP #create backup directory
$TIVOLI_HOME/sbin/ibmslapd -I $INSTANCE -k #stop tds/ldap
sleep 10 # wait to tds/ldap to stop
$TIVOLI_HOME/sbin/idsdbback -I $INSTANCE -n -k $BACKUPDIR/$INSTANCE.$DTSTAMP #backup to
$TIVOLI_HOME/sbin/ibmslapd -I $INSTANCE #start tds/ldap

Daily: create LDIF export of TDS/LDAP
TIVOLI_HOME=/opt/IBM/ldap/V6.1
INSTNAMES="idsinst "
BACKUPDIR=/opt/IBM/ldap/backup/ldif
DTSTAMP=`date '+%Y%m%d%H%M%S'`
# determine last backup file
LASTFILE=`ls -1rt ${BACKUPDIR}/${INSTANCE}*ldif | tail -1`
# create ldif export
$TIVOLI_HOME/sbin/db2ldif -I ${INSTANCE} -o ${BACKUPDIR}/${INSTANCE}.ldif > /tmp/db2ldif.${INSTANCE}.out 2>&1
# compare last ldif export to fresh ldif export
diff ${LASTFILE} ${BACKUPDIR}/${INSTANCE}.ldif > /dev/null
RCdiff=$?
if [[ ${RCdiff} -eq 0 ]]
then
echo "No change to TDS ${INSTANCE} LDIF since last backup -- ${LASTFILE}"
rm ${BACKUPDIR}/${INSTANCE}.ldif
else
echo "Export TDS ${INSTANCE} to LDIF file due to change since last backup"
mv ${BACKUPDIR}/${INSTANCE}.ldif ${BACKUPDIR}/${INSTANCE}.${DTSTAMP}.ldif
fi

Legacy Contributor

Very nice. So the LDIF export can be done while LDAP is in use and the backup requires the LDAP instance to be shut down?

Legacy Contributor

Yes, the LDIF export can be taken while LDAP is online and in use. With the way the LDAP backup script works, yes, the LDAP instance must be shutdown. This LDAP backup script is part of a Unix RC-style script by J David Schronce that starts, stops, restarts, and backs up TDS.

The LDAP backup is part of my weekly Lawson application restart automated routine. The routine is (1) stop IBM HTTPd; (2) stop WebSphere; (3) stoplaw; (4) stop TDS, backup TDS, start TDS; (5) rotate/rename log files (mostly $LAWDIR/system/*log); (6) startlaw; (7) start WebSphere; (8) start IBM HTTPd; (9) remove logs over 90 days old under $IHS_HOME/logs; (10) remove TDS backups over 90 days old.

IBM HTTPd is configured to rotate the access_log and error_log daily.

Legacy Contributor

Ok, so the backup can be done.

What about using the backups you create to perform an actual restore?

moellerg

I've had to do this just once before... not using the ldif export, but with the TDS stopped, backed up, and restarted.
I can't remember exactly what I had to do, but I think it was just to make sure that TDS was down, restore the files (all of them), and restart TDS.

Legacy Contributor

The reason I ask about the restore is because, really, you have to backup not only the Tivoli database, but also the schema and configuration files. All the right and correct way so that you can restore them correctly.

Yes I have created both the backup and restore for Tivoli as a solution for daily backups.

Just think, what would happen if any part of your Tivoli LDAP were corrupted or deleted in some way. How would you recover from it?

todd-brown

Okay we are doing a TDS/ldap shutdown, backup and restart which seems to work fine. However now we are having issues with the lawson env becoming uhnstable and having to bounce the entire env to get fixed. Mainly the lajs becomes unusable and jobs cannot be submitted. We are now up to 10.0.11 esp. Any suggestions or has anyone else seen this?

lmerrill

I've had similar but not exact situation, where lawson environment becomes unstable and I had to bounce the entire env to get fixed. The app server looses connection with database server. Opened several tickets with support, but no resolution.

Robert Canham

I've always stopped the environment before stopping Tivoli. I think at a minimum, you'd have to restart lase.

Legacy Contributor

If you restart TDS, Websphere and Lawson environment should be down before doing that.

If your environment is up and you restart TDS it pulls the rug out from under our processes.
Here is a link to our KB for "Correct Order of Starting and Stopping? Lawson System Foundation (LSF), Landmark (LMRK), Mobile Supply Chain Management (MSCM), Lawson Business Intelligence (LBI) for On-Premise Systems"

https://support.infor.com/espublic/EN/AnswerLinkDotNet/SoHo/SolutionsC/SoHoViewSolution.aspx?SolutionID=1195108

Infor VISUAL Inventory [Phyical Inventory Count].pdf

Legacy Contributor

@robert-canham we don't recommend individually stopping and starting lase using stoplase/startlase.

todd-brown

So you do TDS backups daily weekly? And each time you bounce the Lawson env with WAS too?

monthly_proactive_com201101.pdf

Copyright © 2025 Infor. All rights reserved.