NOTE! The below steps should be performed by users with advanced SQL knowledge. RWS will not be responsible for any data loss caused by incorrectly manipulating SQL databases by the customer.
- Restore the TM Container database from an SQL Backup, by selecting the appropriate backup prior date which would have the missing translation memory. If the restore is on the same SQL ensure to restore with a different name so it does not overwrite the existing Container Database.
- Once the restore is completed ensure the service account of the Groupshare has db_owner role associated to the database
- Once the database is restored, execute the below command on the newly restored Container database to clear all the records from the dbo.resources table.
- delete from dbo.resources
 - NOTE: If the above step is not performed Groupshare will not be able to associate the Container and will give the error "The endpoint or resource doesn't exist"
- Login into the GroupShare Web User Interface and create a new organization using any name.
- Create a new container: go to System Configuration > Containers > + New Container
- For Location specify the newly created organization, give the restored container a name, and for Database Name, use the exact same name of the restored SQL database (use copy-paste to avoid any mismatch).
 - Wait until all TMs from the container are being populated and imported into the new organization. Depending on the number of TMs and their size this process can take several minutes.
- If the TMs are not visible after a while, restore the Container again in the SQL with Replace Option and restart the service.
- Identify the TM that you want to restore/ recreate and run a full export of its content. [ Article Ref ]
- Recreate the TM under your original organization using the same or different TM name. Make sure you will use the same language pair/s and settings.
- Import in it the previously exported content from step 8.
|