• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Wrong command and checks to do before restarting server

E42

New Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
Obsidian
Hello,
There was a moment when I used the command "plesk bin cloning" and later realized that's not what I wanted.

Now, what I want is this: to be able to restart the server and be sure that everything works fine just like now. So, to "undo" the previous command, I used this one:
plesk bin cloning -u -prepare-public-image false -reset-license false -reset-init-conf false

Is this enough? How can I be sure that after a restart nothing will be erased? Thank you and kind regards
 
hello @E42 ,

first of all I'd recommend you to create full Plesk Backup (Tools & Settings > Backup Manager), just in case.


you can check that cloning was canceled by commands below:
:~# plesk bin cloning -s
0
:~# plesk bin cloning -i
prepare-public-image: false
reset-license: false
update-master-key: false
reset-init-conf: false
skip-update: true
maintenance: false

after that I was able to reboot my test Plesk server and everything fine.
 
Back
Top