|
I'm trying to
backup my TMR server, but when I look in the log file of my backup program,
loads of files (some listed below), are showing as being skipped. What
should I do to ensure I get a clean backup of my TMR server?
epmgrlog is
in use. It has been skipped.
gatelog is in use. It has been skipped.
gwdb.bdb is in use. It has been skipped.
gwdb.log is in use. It has been skipped.
imdb.bdb is in use. It has been skipped.
notice.bdb is in use. It has been skipped.
notice.log is in use. It has been skipped.
odb.bdb is in use. It has been skipped.
odb.log is in use. It has been skipped.
odtrace.log is in use. It has been skipped.
oservlog is in use. It has been skipped.
epmgr.bdb\1472981863.1.556.bdb is in use. It has been skipped.
epmgr.bdb\1472981863.1.556.log is in use. It has been skipped.
Contributed
By:
Cliff Hobbs [MVP SMS]
Your problem is being
caused by the fact that Tivoli has the various databases open at the time you
are trying to back them up. Details on backing up the Tivoli database can
be found in Section 2 'Maintaining the Tivoli Database' of the
'Tivoli Management
Framework Maintenance and Troubleshooting Guide'.
You have several options for your
backups such as:
- Scheduling Tivoli to do the
backups for you and then having your backup program backup the contents of the
'backups'
directory created by Tivoli (the name and location of which you can change)
- If you don't want to set this
up in Tivoli, or give the people performing backups access to Tivoli so they
can invoke the 'wbupdb'
command, simply tell them to stop the oserv service, allow the backup program
to backup the Tivoli files and then start the oserv service.
Remember that as no
Tivoli-related data is stored on the Endpoints, you only need to backup your
TMRs and Managed Nodes as part of your Tivoli backups.
|