IIB mqsibackupbroker command

IIB mqsibackupbroker command details below for reference,

mqsibackupbroker command is used to backup the configuration of broker. Below are the command attributes,

As mentioned in IBM Integration Bus v9 knowledge center,

The command backs up of the following persistent configuration data associated with the broker:

Deployed resources; message flows, dictionaries, JAR files, and other runtime resources that you have previously               deployed in a BAR file.
Integration servers.
Broker configuration; for example, configurable services.

The command does not back up the following resources:

Transient information; for example, inflight aggregations or collections.
Executable code, including resources that are associated with user-defined extensions (nodes, parsers, and exits).
Resources required by message flows to function correctly

Please make a note of below points as these are vital during backup process,

• Use the backup file to restore a broker on a computer that has an identical configuration; the operating system must be at the same level, and the broker and queue manager names must be identical.
• You can run this command for a broker that is active. However, you must not take a backup while the broker is processing configuration changes and deployments; the backup file created might contain incomplete information. If the file contains partial records, you cannot use it to restore the broker at a later time.
• To ensure that the backup is complete and correct, either take a backup when the broker is not processing a configuration change (such as a deployment or change property) or when the broker is stopped.

Command parameters,

mqsibackupbroker <parameters>

brokerName
(Required attribute) The name of the broker that you want to back up. You must specify the name as the first parameter.
-d directory
(Required) The directory in which the backup file is created. You must specify a directory that is on a file system that can be accessed by the computer on which you run this command.
-a archiveName
(Optional) The name of the backup (archive) file. The file is created in compressed file format. If you do not specify this parameter, the default name brokerName_yyMMdd_HHmmss.zip is used.
-v traceFileName
(Optional) The location of a trace file that records details of the actions taken by the command.
-f
(Optional) Force incomplete backup files to be created if one or more parts of the broker configuration cannot be read.

Command screenshot below,

on linux it would be the same kind of command where we provide,
mqsibackupbroker broker1 -d /tmp/brokerbackup -a broker1bkp_21072017.zip -v broker1bkp_21072017.log

I don’t see much difference in implementation of this command in IBM Integration Bus v10. Its same across both versions, where they mentioned Integration Node rather Broker. Refer to IIB v10 knowledge center link here.