• 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!
  • 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.

Site database backup filename may not match database name

RationalPolymer

Basic Pleskian
Is it normal where a site/domain backup with a database has a database tar file whose name is similar but different from the actual site/domain database name? For example: 'blogs_wordpress_3' database but 'blogs_wordpres_8' database backup filename.

The backup INFO.xml file will contain both names so there doesn't appear to be any problem with backing up and restoring the same/proper/expected database, but it is somewhat confusing when looking at the backup files and seeing a difference in the database filenames versus the database name.

If this is "normal" then how/when/why does it occur?
 
Back
Top