Commented by: @AlexPeshkoff

When working with this issue, I've found that stdout and stderr are incorrectly mixed in services, making some services return errors in status vector (correct behavior), others (like mentioned gbak) - as text in same way as verbose information is returned. To fix that crap, all data sent by services/utilities (this is same thing for us) was divided into 3 classes: errors, verbose info and binary data.

When working as standalone utility errors are printed to stderr, verbose messages go to stdout. But when utility is outputting binary data to stdout (looks like only gbak can do it now?), verbose info also goes now to stderr.

When working as service, utility does not print error messages - it sends status vector to services manager, verbose info is delivered to the user. When utility decides to send binary data to the user (only gsec does it now), delivery of verbose info should not be done. Cause gsec has no verbose info at all, no problems with it now. But when doing server-site backup (issue 2666), one more careful review of gbak may be needed.

Commented by: @AlexPeshkoff

When doing server-site backup, it's critical not to mix gbak data with some messages, possibly generated by gbak.