• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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