Replicating Schema/Table using Vbr copies files stored on disk. Since those files are already in a compressed format, Replicating objects is generally faster than exporting and importing objects.
Thank you!
This topic is related to this one https://forum.vertica.com/discussion/240553/maximum-number-of-ros-containers#latest
I have made a lot of mergeout operations in order to decrease the number of ROS containers. This number has decreased dramatically from 2500 to 1. As consequence, the replication process that initially lasted 30 min , now needs 9 h. Practically, the amount of bytes to copy is equivalent to the table size. Thus, I was thinking, the replication is done at file level.
I my case, the solution was to backup/restore (object level), manually, the table on the second server. Thus, wasn't necessary to replicate the big file.
After this manual restore, the replication lasted 15 min.
Comments
Replicating Schema/Table using Vbr copies files stored on disk. Since those files are already in a compressed format, Replicating objects is generally faster than exporting and importing objects.
Hi @vcarusi,
Vertica supports replication at the object level. See this link for more details - https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/AdministratorsGuide/BackupRestore/ReplicatingtoanAlternateCluster.htm?tocpath=Administrator's Guide|Backing Up and Restoring the Database|_____30
Thank you!
This topic is related to this one
https://forum.vertica.com/discussion/240553/maximum-number-of-ros-containers#latest
I have made a lot of mergeout operations in order to decrease the number of ROS containers. This number has decreased dramatically from 2500 to 1. As consequence, the replication process that initially lasted 30 min , now needs 9 h. Practically, the amount of bytes to copy is equivalent to the table size. Thus, I was thinking, the replication is done at file level.
I my case, the solution was to backup/restore (object level), manually, the table on the second server. Thus, wasn't necessary to replicate the big file.
After this manual restore, the replication lasted 15 min.