It's all about the answers!

Ask a question

RTC External Content Repository scenario


Arun K Sriramaiah (3.2k13277) | asked Jul 01 '19, 4:21 a.m.
edited Jul 01 '19, 4:22 a.m.


https://jazz.net/library/article/90403   

Needs to reduce the RTC database size (8 TB) and he's thinking to the external content repositories feature.

The goal is to reduce the database size at 1 TB so, want to move 7TB of data to the filesystem. In order to reduce the complexity to manage a 7TB filesystem, the idea is to have different filesystems (for example 7 filesystem of 1 TB).

Questions:

Is this configuration supported? if Yes,
Do we have any options to rotate the folder after 1 TB in size?
Do we see any attention point?

One answer



permanent link
Arun K Sriramaiah (3.2k13277) | answered Jul 01 '19, 4:24 a.m.

Best possible available solution and details


1) Is this configuration supported:
    It is not supported to spread a single external content repository over multiple filesystems
        If they want to do this, they should look for some kind of Virtual Volume solution that can manage multiple volumes and present them as a single virtual container.  Artifactory can also manage adding storage to the content store.
        
    We do not recommend simply mounting multiple filesytems under a single root.
    
2) Do we have any options to rotate the folder.

        Yes.  The location of the external content root can be changed. Existing content at the old location remains accessible to users, assuming the old location still exists and is accessible by the server.   New content will be stored at the new content location.
        
3) Other issues?

    - We have seen linux mount points fail to mount, which leaves the RTC server writing to the filesystem where the mount point is rather than to the other filesytem which was intended to be mounted.  
This represents a potential for data loss which is why we don't recommend splitting the external content store over multiple volumes without proper management software.
    - Delta compression is only used on content stored in the database.  Content stored in an external content repository will only be stored raw or gzipped (whichever is smaller).  This means content may potentially take up more space when stored externally.
  

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.