[
https://issues.apache.org/jira/browse/OPENMEETINGS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SebastianWagner updated OPENMEETINGS-446:
-----------------------------------------
Labels: Backup Import (was: )
> Create a Master backup File for last versions (including all generated data)
> ----------------------------------------------------------------------------
>
> Key: OPENMEETINGS-446
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-446
> Project: Openmeetings
> Issue Type: Task
> Reporter: SebastianWagner
> Assignee: SebastianWagner
> Priority: Critical
> Labels: Backup, Import
>
> We need to test if our old backups still import right.
> A backup should contain:
> 1) Multiple user records, while minimum 1 user is bound to an organization
> 2) Multiple room records, while minimum 1 room is bound to an organization
> 3) There has to be at least 1 user that has generated private messages,
> contacts and calendar events
> 4) There has to be at least 1 conference room that has files and folders in
> the private and public section
> 5) There has to be at least 1 poll in a conference room
> 6) There has to be at least 1 recording made of a conference room
> 7) There has to be at least 1 interview recorded
> 8) There has to be created at least 1 folder in the recording section in the
> private and public share
> 9) There has to be at least 1 (maybe inactive) Ldap config stored in the LDAP
> configuration admin section
> We need backups starting from Version:
> OpenMeetings 1.4 RC1
> OpenMeetings 1.5 RC1
> OpenMeetings 1.6.2 (since 1.6 the backup does contain recordings and uploaded
> files)
> OpenMeetings 1.7
> OpenMeetings 1.8.8
> OpenMeetings 1.9.1
> OpenMeetings 2.0
> After we have created the Backups, we can start testing importing them into
> current trunk and verify if the user generated data is available after the
> import.
> The backups should be made available somewhere, either Wiki or SVN. SVN might
> be the better place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
