Bug #36607 backup is created when specifying "no" to backup during monitor update install
Submitted: 9 May 2008 1:03 Modified: 3 Mar 2009 21:22
Reporter: Bill Weber Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version:1.3.1, 1.2.1 OS:Any
Assigned to: Andy Bang CPU Architecture:Any

[9 May 2008 1:03] Bill Weber 
Description:
If "No" is specified for the "Do you want to backup your existing data..." question on the "Backup of Previous Installation" page of the monitor uninstall, a backup directory is created and all previous files are copied into it anyway.

How to repeat:
- install 1.3.0 monitor
- run 1.3.1 update installer
- click "No" for the "Do you want to backup your existing data..." question on the "Backup of Previous Installation" page
- finish installing the monitor
| see that a backup directory was created
[9 May 2008 2:08] Bill Weber 
this is also the same for the 1.2.1.9071
[9 May 2008 15:44] Andy Bang 
I can confirm that at least on Windows it behaves as Javier says.  If you say "No", it does create a backup of the application, but it does not create a backup of the merlin database and associated InnoDB files (it only creates a backup of the mysql data, which is quite small).
[9 May 2008 16:14] Andy Bang 
During bug council we decided to handle this as a simple wording change.
[20 Nov 2008 18:59] Andy Bang 
Per a conversation with Bill, I changed the first question on that screen from:

Where should Setup put a backup of your previous installation?  Please refer to the README file for information regarding backup and recovery.

to:

Where should Setup put a backup of the application files for your previous installation?  Please refer to the online documentation for information regarding backup and recovery.
[3 Mar 2009 21:22] Marcos Palacios 
Verified fixed in build 2.0.0.7122.