2016-12-13 20:07:20.0249 java.lang.NullPointerException
at com.ibm.broker.config.util.BackupBroker.runCommand(BackupBroker.java:591)
at com.ibm.broker.config.util.BackupBroker.main(BackupBroker.java:752)
2016-12-13 20:07:20.0473 com.ibm.broker.config.util.ConfigUtilityException: BKR01<<null
at com.ibm.broker.config.util.BackupBroker.runCommand(BackupBroker.java:663)
at com.ibm.broker.config.util.BackupBroker.main(BackupBroker.java:752)
2016-12-13 20:07:20.0474 Exiting with return code 253 - derived from encountered BIP1253
I searched in google the BIP1253 code and i found this:
Quote:
Backing up or restoring the broker returns error BIP1253 or BIP1262
Scenario: An error message is generated when you back up or restore a broker:
The following message is returned when you run the mqsibackupbroker command:
BIP1253E Failed to backup the broker 'broker_name' (error 'error_code')
The following message is returned when you run the mqsirestorebroker command:
Code:
BIP1262E Could not delete the existing configuration of broker 'broker_name'.
Explanation: Both backup and restore commands require read/write access to the files that contain broker configuration data. Access has failed and the command cannot complete its operation successfully.
Solution: Typically, you might see one of these errors if you are running the backup or restore command against an active broker, and a conflict of access has occurred. If your broker is active, use the mqsistop command to stop the broker, and try the operation again.
You might also see one of these errors if the directory to which the command is writing, or from which it is reading, is temporarily inaccessible because of communications or authorization problems. Check that your user ID has access to the directory that you specified in the command.
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
This
Code:
At least one file in the broker's configuration could not be backed up.
Seems pretty clear to me.
Have you checked the user and group ownership of ALL the files in the Broker Tree?
Perhaps one got 'modified' by hand and had its attributes changed.
You could write a shell script to check for you
List ( ls -la) all the files in every directory (ls -laR) and feed it into grep where you look for a pattern that does not include 'mqbrkrs' and the appropriate user name.
Have you tried to create a new broker (different name) and get a backup of it?
Does this work? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum