[jira] [Commented] (AMBARI-354) hmc rpm on install must backup the database

["Suresh Srinivas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279858#comment-13279858 ] 

Suresh Srinivas commented on AMBARI-354:
----------------------------------------

Use cases to consider:
*Use case 1 - User uninstalls rpm accidentally and re-installs it again.*
During uninstall, the db file is backed up. The existing data directory is removed. A documented procedure will tell the user how to restore the db file post re-install to go back to the previous state.

*Use case 2 - User uninstalls rpm to cleanup the install and re-install it back.*
During uninstall, the db file is backed up. The existing data directory is removed. During a re-install a new db file is created. User can go on to configure the cluster (on the masterd).

*Use case 3 - User upgrades to new release. Old rpm is uninstalled.*
New release *must* install the files in a new directory. This way uninstall of old rpm does not delete the data directory corresponding to the new release install.

                
> hmc rpm on install must backup the database
> -------------------------------------------
>
>                 Key: AMBARI-354
>                 URL: https://issues.apache.org/jira/browse/AMBARI-354
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: ambari-186
>            Reporter: Suresh Srinivas
>         Attachments: AMBARI-354.txt
>
>
> HMC rpm during install must backup the database lingering from previous installs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira