Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    7
  • Subscribers subscribers
    15
  • Views views
    511
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Relocate the FiLR-DB

Ascan

Hi,

there is a long running FiLR (small Deployment). It comes from FiLR 1.1 and is upgraded each time with the newest version. So this Small Deployment is now version 5.0.0.2)

Now we want to separate the DB. This should be the separate DB-VA.

1. Setup the DB-VA (edit pg_hba.conf so that the FiLR-VA can access.)

2. Export the DB-Data (Stop FiLR; pg_dump -d filr -U filr -C > DB-dump.sql)

3. Create the FiLR-DB with the Postgres-Webinterface. Import the DB-Dump at the new DB-VA (psql filr -U filr < DB-dump.sql) (same DB-Name, same user, same password)

4. Edit the configuration at the FiLR-VA to access the external DB. (and stop the embedded DB)

As the result I can login to FiLR but the most of the users are not visible (in admin/users). And no user see the networks folders.

I miss all external users (self created login), all buildIn accounts and the most  -but not all- of the via LDAP-Sync imported users.

Has anybody done this relocate of the DB before and can give an advice?

Parents
  • 0  

    As far as I can see you did all steps in the right way.

    I recommend to run a re-index (administration console). 

    Use "Verified Answers" if your problem/issue has been solved!

  • 0   in reply to   

    I agree that this appears to have been done much the same I usually do it.

    Some comments.

    Re point 1.  By default the the database appliance is open to all, vabase-pg_hba.conf  has the line "host    all    all    0.0.0.0/0    md5"  I usually mofify this so only the filr Web Appliances and admin can connect to the database.

    Re point 2, I usually move the database directly from old to new using

    1. pg_dump -U filr –d filr | psql -h <remotehost> -U filr -d filr
    2. Enter password twice then Ctrl-D to logout when finished

    Or

    1. PGPASSWORD=<password1> pg_dump -U filr –d filr | PGPASSWORD=<password2> psql -h <remotehost> -U filr -d filr
    2. Ctrl-D to logout when finished
    3. Use a space beforehand so it is not stored in the history
Reply
  • 0   in reply to   

    I agree that this appears to have been done much the same I usually do it.

    Some comments.

    Re point 1.  By default the the database appliance is open to all, vabase-pg_hba.conf  has the line "host    all    all    0.0.0.0/0    md5"  I usually mofify this so only the filr Web Appliances and admin can connect to the database.

    Re point 2, I usually move the database directly from old to new using

    1. pg_dump -U filr –d filr | psql -h <remotehost> -U filr -d filr
    2. Enter password twice then Ctrl-D to logout when finished

    Or

    1. PGPASSWORD=<password1> pg_dump -U filr –d filr | PGPASSWORD=<password2> psql -h <remotehost> -U filr -d filr
    2. Ctrl-D to logout when finished
    3. Use a space beforehand so it is not stored in the history
Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.