Should we be running suspendindexer before backing up database?
During a CLM upgrade we want to first quiesce and backup the database and environment.
We have been: suspending the idexes, stopping the apps (in websphere), backing up the db and server environment. Is suspendindex overkill here? is the stopping the application sufficiently graceful or does the suspendindex step add some value? |
Accepted answer
Suspendindex is only required in v3.0.x JFSIndexes backup if you don't want to shut down the server. The benefit to use suspendindex is to reduce downtime. In v4.0.x, there is a repotools command for JFSIndexes backup(for example: repotools-jts -backupJFSIndexes) so you don't need to suspendindex to avoid corruption even you want to online backup JFSIndexes. Basically if you stop the servers, you don't really need to suspendindex even though it is in v3.0.x.
More explanation is in this article: https://jazz.net/library/article/795 Virginia Brown selected this answer as the correct answer
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.