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 Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    14
  • Views views
    408
  • 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

HA Filr 23+ - Good practice and TIP to have a rock solid Filr large deployment

wlucero
 

Good afternoon community!

On this occasion I come to you with the spirit of being able to outline what would be the best practices to be able to achieve a very robust installation of Filr.
We have a very critical customer in LATAM that will be growing exponentially soon. 

This customer has purchased Filr Advanced licenses and has the following architecture with 8 servers and couting (growing):

General notes: 

  • This virtual appliances are running on a vmware cluster protected with Veeam.
  • Today all the netfolders are publishing information from their Microsoft NAS, but the idea is to return (migrate-move) all that information directly to Filr in order to eliminate the point of failure they have with Microsoft and at the same time achieve the same effect and sensation users have when using Dropbox, without the need for a sysadmin managing security on an NTFS Filrsystem.

We understand that we must strengthen the points marked with a red cross and question mark:

Could share advice, information and references about:

  1. With the purchased Filr Advance licenses, could you have your PostgreSQL base replicated against another DB appliance?
  2. Recommended procedures to backup PostgreSQL Filr database?.
  3. Recommended procedures to backup the NFS /vashare?

I look forward to your input and ideas! THANKS in advance!

Hugs.,Muscle

  • Verified Answer

    +1  

    1 I tend to do do realtime replication to a second db appliance, this way your backup is only a second or so behind the live system and it takes only a few seconds to switch the secondary to be the primary

    2. I feel the replication way is best,because it is more or less real time but you can also pg dump, backup the vastorage disk or backup the whole vm. 

    3. vashare I would use whatever your standard backup software is., you could also use something like rsync and only do delta backups. as the vast majority or vashare does not change

  • 0   in reply to   

    Hey Robin!, how are you?. THANKS for your feedback!!!. 

    Questions:

    1) With the current licensing (Filr Advance licenses), we could deploy and set up a new and 2nd FilrDB appliance and then configure a realtime replication right?. Do you have a document or a procedure that we can use as a reference?

    2) Agreed

    3) Got it. 

    4) When you have time, could you share the document on how you recommend making a backup of Filr? I remember seeing it but I can't find it. This will help us to have backup covered while we analyze / study the replication scenario.

    Have a great day Robin!. Muscle

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.