How can I remotely clean up expired and expired backups on 48 MySQL DB servers in Production? How can I remotely clean up expired and effective backups on 48 MySQL DB servers! At first, I thought of entering ssh from the control machine one by one, rm drop, then exit, and then ssh Through the control machine, and rm then exit. In this case, I would not need to perform ssh and exit 48 times, 48 servers are acceptable. What if there are 480 and 4800 servers? any way? OK, I thought of it. Write a shell script and remotely execute the ssh command on the control machine. You do not need to ssh to a specific single database, as shown in the following clean. sh [html] ssh aaaaaaaaa048xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa047xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa046xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa045xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa044xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa043xxxxxx "s Udo-u mysql du-sh/mysqlback/* "; ssh aaaaaaaaa042xxxxxx" sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa041xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa040xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa039xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa038xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa037xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh Aaaaaaaa036xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa035xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa034xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa033xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa032xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa031xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa030xxxxxx "sudo-u mysql du-sh /Mysqlback/* "; ssh aaaaaaaaa029xxxxxx" sudo-u mysql du-sh/mysqlback/* "; ssh aaaaaaaaaaa028xxxxxx" sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa027xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa026xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa025xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa024xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa023xxxxxx "s Udo-u mysql du-sh/mysqlback/* "; ssh aaaaaaaaa022xxxxxx" sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa021xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaaaa020xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa019xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa018xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa017xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh Aaaaaaaa016xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa015xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa014xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa013xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa012xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa011xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa010xxxxxx "sudo-u mysql du-sh /Mysqlback/* "; ssh aaaaaaaaa009xxxxxx" sudo-u mysql du-sh/mysqlback/* "; ssh aaaaaaaaa008xxxxxx" sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa007xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa006xxxxxx "sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaaaa005xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa004xxxxxx "sudo-u mysql du-sh/mysqlback/*"; ssh aaaaaaaaa003xxxxxx "s Udo-u mysql du-sh/mysqlback/* "; ssh aaaaaaaaa002xxxxxx" sudo-u mysql du-sh/mysqlback /*"; ssh aaaaaaa001xxxxxx "sudo-u mysql du-sh/mysqlback/*"; PS: 1 ssh aaaaaaaaa001xxxxxx "sudo-u mysql du-sh/mysqlback /*"; this indicates that check whether the backup has been deleted. You can change du-sh/mysqlback/* "to rm-rf to clear the file. 2. I do not need a password for ssh here. If you need to enter a password for verification for ssh, try again: ssh pass-p 'Password' sshroot@xx.com "command" command run this clean script, I here ssh into aaaaaaaaaaa001xxxxxx does not need a password, and because the db server also needs to switch to the mysql account, otherwise, you cannot use rm to operate mysql user group files. Sudo-u mysql prefix is used in the remote command.