Hi Harish, I tried using the link below to export and import AAI DB from one Amsterdam deployment, to another Amsterdam deployment, and it worked.
However, some branches were not imported from Amsterdam to Amsterdam, but it was OK, as the important branches were imported. We are now planning to migrate our application to work on Beijing. We exported the snapshot from Amsterdam using the latest snapshot file under /opt/app/aai-resources/logs/data/dataSnapshots. Then, we tried to import the snapshot in Beijing using the command in the link https://wiki.onap.org/pages/viewpage.action?pageId=33065587https://wiki.onap.org/pages/viewpage.action?pageId=33065587 docker exec -u aaiadmin -it dev-aai-resources-d489cd699-xw9qj_1 /opt/app/aai-resources/bin/dataRestoreFromSnapshot.sh dataSnapshot.graphSON.201806191500 Note that we are using OOM, so we used the pod for aai-resources. The script showed us that a snapshot was created, and the database was cleared, re-created the schema, and imported the database, no errors. However, the data was not imported to AAI Beijing, and when we checked the logs in /opt/app/aai-resources/logs/dataSnapshot/error.log, we can see the errors below. Is it the correct process to use a snapshot from Amsterdam and import in Beijing ? Is AAI Beijing backward compatible with Amsterdam ? 2018-06-19T10:32:23.723+0000|2018-06-19T10:32:23.723+0000|f385be18-4ccd-4fd0-9d83-9c8e743fae88||main ||AAI|NA|COMPLETE||||WARN|||0|||org.janusgraph.core.util.ReflectiveConfigOptionLoader|||||||co=config:given scan urls are empty. set urls in the configuration 2018-06-19T10:32:24.261+0000|2018-06-19T10:32:24.261+0000|f385be18-4ccd-4fd0-9d83-9c8e743fae88||main ||AAI|NA|COMPLETE||||WARN|||0|||org.janusgraph.core.JanusGraphFactory|||||||co=config:Local setting cache.db-cache-clean-wait=20 (Type: GLOBAL_OFFLINE) is overridden by globally managed value (50). Use the ManagementSystem interface instead of the local configuration to control this setting. 2018-06-19T10:32:24.272+0000|2018-06-19T10:32:24.272+0000|f385be18-4ccd-4fd0-9d83-9c8e743fae88||main ||AAI|NA|COMPLETE||||WARN|||0|||org.janusgraph.core.JanusGraphFactory|||||||co=config:Local setting cache.db-cache-time=180000 (Type: GLOBAL_OFFLINE) is overridden by globally managed value (10000). Use the ManagementSystem interface instead of the local configuration to control this setting. 2018-06-19T10:32:30.158+0000|2018-06-19T10:32:30.158+0000|f385be18-4ccd-4fd0-9d83-9c8e743fae88||main ||AAI|NA|COMPLETE||||ERROR|||0|||com.netflix.astyanax.AstyanaxContext|||||||co=config:com.netflix.MonitoredResources:type=ASTYANAX,name=KeyspaceJanusGraphConnectionPool,ServiceType=connectionpool 2018-06-19T10:32:30.159+0000|2018-06-19T10:32:30.159+0000|f385be18-4ccd-4fd0-9d83-9c8e743fae88||main ||AAI|NA|COMPLETE||||ERROR|||0|||com.netflix.astyanax.AstyanaxContext|||||||co=config:com.netflix.MonitoredResources:type=ASTYANAX,name=ClusterJanusGraphConnectionPool,ServiceType=connectionpool 2018-06-19T10:32:46.103+0000|2018-06-19T10:32:46.103+0000|7c8e351a-7bbf-480c-a2e6-73a3384243b7||main ||AAI|NA|COMPLETE||||WARN|||0|||org.janusgraph.core.util.ReflectiveConfigOptionLoader|||||||co=config:given scan urls are empty. set urls in the configuration 2018-06-19T10:32:46.769+0000|2018-06-19T10:32:46.769+0000|7c8e351a-7bbf-480c-a2e6-73a3384243b7||main ||AAI|NA|COMPLETE||||WARN|||0|||org.janusgraph.core.JanusGraphFactory|||||||co=config:Local setting cache.db-cache-clean-wait=20 (Type: GLOBAL_OFFLINE) is overridden by globally managed value (50). Use the ManagementSystem interface instead of the local configuration to control this setting. 2018-06-19T10:32:46.773+0000|2018-06-19T10:32:46.773+0000|7c8e351a-7bbf-480c-a2e6-73a3384243b7||main ||AAI|NA|COMPLETE||||WARN|||0|||org.janusgraph.core.JanusGraphFactory|||||||co=config:Local setting cache.db-cache-time=180000 (Type: GLOBAL_OFFLINE) is overridden by globally managed value (10000). Use the ManagementSystem interface instead of the local configuration to control this setting. 2018-06-19T10:32:48.438+0000|2018-06-19T10:32:48.438+0000|7c8e351a-7bbf-480c-a2e6-73a3384243b7||main ||AAI|NA|ERROR|500|Unexpected error:3000:Internal Server Error:Adding this property for key [model-version-id] and value [5a175add-57e4-4a5d-8b02-c36f1d69c52b] violates a uniqueness constraint [model-version-id]||ERROR|||0|||com.netflix.astyanax.AstyanaxContext|||||||co=config:com.netflix.MonitoredResources:type=ASTYANAX,name=KeyspaceJanusGraphConnectionPool,ServiceType=connectionpool 2018-06-19T10:32:48.439+0000|2018-06-19T10:32:48.439+0000|7c8e351a-7bbf-480c-a2e6-73a3384243b7||main ||AAI|NA|ERROR|500|Unexpected error:3000:Internal Server Error:Adding this property for key [model-version-id] and value [5a175add-57e4-4a5d-8b02-c36f1d69c52b] violates a uniqueness constraint [model-version-id]||ERROR|||0|||com.netflix.astyanax.AstyanaxContext|||||||co=config:com.netflix.MonitoredResources:type=ASTYANAX,name=ClusterJanusGraphConnectionPool,ServiceType=connectionpool Thanks A. Seaudi ________________________________ From: KAJUR, HARISH V [vk2...@att.com] Sent: Thursday, May 17, 2018 7:15 PM To: onap-discuss@lists.onap.org Cc: SEAUDI Abdelmuhaimen OBS/CSO; FORSYTH, JAMES Subject: [onap-discuss] How to backup AAI database records Hi, In Amsterdam, we created a cron job so when you spin it up using heat template, it would take a backup hourly of the data. If they have it using Amsterdam of heat template, then their data should have been stored in /opt/aai/logroot/AAI-RESOURCES/data/dataSnapshots/ in aai vm1. Also, the wiki was created for Amsterdam release how to take a snapshot and do restore manually https://wiki.onap.org/pages/viewpage.action?pageId=15998201 Here is the wiki on how to do this in beijing release https://wiki.onap.org/pages/viewpage.action?pageId=33065587 Thanks, Harish _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
