What are all the basic methods that we should uphold to migrate/refresh the data from one clarity env to other env.
Curious to know the end-to-end steps and best practices invloved in migrating the data/refresh from one clarity env to other env.(Say from PROD to DEV of same version/different version)
Waiting eagerly for your comments!
Xog is the best way to do it in my opinion which maintains the data integrity
Thanks for ur reply.
I agree to ur point xog would be best way to do it, since it will take care of many unknown background process which are hindered for normal users.
Xogging out an custom object from one env and xogging in to other env is always a best option.
But think of just data, imagine that i have close to 1million records related to investments stored in oracle DB(inv_investments,etc..) in OOTB clarity env and i wanted to move it from PROD to DEV, do we have any handy method to move this big volume of data?...
Have you checked this thread ?
And these -
Migrate to On Demand
Backup Clarity data and restore it to different server
Why would you need to migrate from one clarity to other rather upgrade the system and they will take care. Data movement from one environment from other remains tedious and again xog is the best way forward and in 13.3 you have xml node configuration which will save you from out of memory issues.
To support development activities based on the data in PROD, we wanted to back up data from PROD to Dev.
If its same version then you can refresh the database from prod to dev if its samea version and take the back up of all the new customization/configurations.
Here's a redacted version of what we do.
I have recently migrated configuration/data from clarity SQL Server to Clarity Oracle server by using XOG (around 300 GB data). But time lines is little bit high.
Here is another post detailing the challenges for 13.3
Have you tried reaching out to the CA Services Global Delivery team for the Data Migration tool ?
Thank you all ur thoughts.
As we are in oracle DB enterpise ed, suggestion from DBA was to go with database backup and recovery using RMAN
That should be ok, its better to go with cold back up.
We have plan to move from Oracle to SQL Server in near future due to company policies. Approximately how much time you have spent in this activity.
Our Current Version is Clarity 8 with Oracle 9i
Target version is Clarity 14 with SQL Server 2014
Time line will be based on size of DB & documents.
Also on how much custom items, custom configuration, add ons and customization and may vary between organization and quality of plan.
Upgrade strategy for 188.8.131.52 to 14.1
for steps you might have not thought of.