Bug 1191792 - mariadb binlog server service file
Summary: mariadb binlog server service file
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Danilo Spinella
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-18 15:19 UTC by Marcus Rückert
Modified: 2022-10-20 18:49 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Rückert 2021-10-18 15:19:22 UTC 
mariadb-mysqlbinlog.service

mysqlbinlog --read-from-remote-server --host=host_name --raw
  --stop-never 

this would make it easy to run a binlog backup server.
Comment 1 Danilo Spinella 2021-11-08 14:45:10 UTC 
That would be a good idea, maybe a mariadb-mysqlbinlog@.service, using the instance as hostname? E.g. mariadb-mysqlbinlog@example.com. 

However, I am not sure if it would be better to let admins create this service file when they need it or providing it to all users. Can you please open an issue upstream (jira.mariadb.com) so that we can discuss this service with MariaDB devs? Thank you!
Comment 2 Marcus Rückert 2022-10-17 09:41:30 UTC 
This is something probably every admin of a bigger instance should run for point in time recovery. so yes i think we should ship it and then upstream that file.
Comment 3 Danilo Spinella 2022-10-20 18:49:12 UTC 
Created upstream issue:

https://jira.mariadb.org/browse/MCOL-5274