{"id":93878,"date":"2020-09-10T19:42:02","date_gmt":"2020-09-10T17:42:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kak-vpisat-svobodnuyu-postgresql-v-surovoe-enterprise-okruzhenie"},"modified":"2020-09-10T19:42:02","modified_gmt":"2020-09-10T17:42:02","slug":"kak-vpisat-svobodnuyu-postgresql-v-surovoe-enterprise-okruzhenie","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vpisat-svobodnuyu-postgresql-v-surovoe-enterprise-okruzhenie","title":{"rendered":"Si t\u00eb integroni PostgreSQL \u00abt\u00eb lir\u00eb\u00bb n\u00eb nj\u00eb mjedis t\u00eb ashp\u00ebr enterprise","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Shumica e njer\u00ebzve jan\u00eb t\u00eb njohur me DBMS PostgreSQL, dhe ajo ka treguar performanc\u00ebn e saj t\u00eb shk\u00eblqyer n\u00eb instalimet e vogla. Megjithat\u00eb, tendenca p\u00ebr t\u00eb kaluar n\u00eb Open Source \u00ebsht\u00eb b\u00ebr\u00eb gjithnj\u00eb e m\u00eb e qart\u00eb, madje edhe kur b\u00ebhet fjal\u00eb p\u00ebr kompanit\u00eb e m\u00ebdha dhe k\u00ebrkesat enterprise. N\u00eb k\u00ebt\u00eb artikull, do t\u00eb flasim se si t\u00eb integromi Postgres n\u00eb nj\u00eb ambient korporat\u00eb dhe do t\u00eb ndajm\u00eb p\u00ebrvoj\u00ebn ton\u00eb n\u00eb krijimin e nj\u00eb sistemi t\u00eb kopjeve rezerv\u00eb (SRK) p\u00ebr k\u00ebt\u00eb baz\u00eb t\u00eb dh\u00ebnash duke marr\u00eb shembullin e sistemit t\u00eb kopjeve rezerv\u00eb Commvault. <\/p>\n

\"Si
\nPostgreSQL ka d\u00ebshmuar q\u00eb \u00ebsht\u00eb e besueshme \u2014 DBMS funksionon n\u00eb m\u00ebnyr\u00eb t\u00eb shk\u00eblqyer, e p\u00ebrdorin biznese moderne digjitale si Alibaba dhe TripAdvisor, dhe mungesa e tarifave t\u00eb licenc\u00ebs e b\u00ebn at\u00eb nj\u00eb alternativ\u00eb t\u00ebrheq\u00ebse ndaj gjigant\u00ebve si MS SQL ose Oracle DB. Por sa her\u00eb q\u00eb fillojm\u00eb t\u00eb mendojm\u00eb p\u00ebr PostgreSQL n\u00eb peizazhin e Enterprise, p\u00ebrballemi me k\u00ebrkesa t\u00eb rrepta: \"Si \u00ebsht\u00eb q\u00ebndrueshm\u00ebria e konfiguracionit? si p\u00ebr q\u00ebndrueshm\u00ebri t\u00eb fatkeq\u00ebsive? ku \u00ebsht\u00eb monitorimi i gjithansh\u00ebm? a ka backup automatizuar? a p\u00ebrdoren bibliotekat e kasetave si direkt ashtu edhe si depo sekondare?\"
\n<\/a><\/noindex>
\n\"Si
\nNga nj\u00ebra an\u00eb, PostgreSQL nuk ka mjete t\u00eb integruara p\u00ebr backup, si\u00e7 ka DBMS t\u00eb \"rritura\" si RMAN n\u00eb Oracle DB ose SAP Database Backup. Nga ana tjet\u00ebr, ofruesit e sistemeve t\u00eb kopjeve rezerv\u00eb p\u00ebr kompanit\u00eb (Veeam, Veritas, Commvault) megjithat\u00eb mb\u00ebshtesin PostgreSQL, por praktikisht punojn\u00eb vet\u00ebm me nj\u00eb konfigurim t\u00eb caktuar (zakonisht standalone) dhe me nj\u00eb grup kufizimesh t\u00eb ndryshme. <\/p>\n

Sistemet e kopjeve rezerv\u00eb t\u00eb dizajnuar posa\u00e7\u00ebrisht p\u00ebr PostgreSQL, si Barman, Wal-g, pg_probackup, jan\u00eb jasht\u00ebzakonisht t\u00eb njohura n\u00eb instalimet e vogla t\u00eb DBMS PostgreSQL ose atje ku nuk nevojiten kopje t\u00eb m\u00ebdha t\u00eb elementeve t\u00eb tjera t\u00eb peizazhit IT. P\u00ebr shembull, p\u00ebrve\u00e7 PostgreSQL, n\u00eb infrastruktur\u00eb mund t\u00eb jen\u00eb fizike dhe virtuale, OpenShift, Oracle, MariaDB, Cassandra, etj. T\u00eb gjitha k\u00ebto d\u00ebshirojn\u00eb t\u00eb kopjohen me nj\u00eb mjet t\u00eb p\u00ebrbashk\u00ebt. T\u00eb vendos\u00ebsh nj\u00eb zgjidhje t\u00eb ve\u00e7ant\u00eb vet\u00ebm p\u00ebr PostgreSQL \u00ebsht\u00eb nj\u00eb ide e keqe: t\u00eb dh\u00ebnat do t\u00eb kopjohen diku n\u00eb disk dhe pastaj duhet t\u2019i transferosh n\u00eb kaset\u00eb. Ky dyfishim i kopjimit rezerv\u00eb rrit koh\u00ebn e kopjimit, dhe m\u00eb e r\u00ebnd\u00ebsishmja, - rikuperimin. falas. Kjo \u00ebsht\u00eb vet\u00ebm nj\u00eb nga shum\u00eb privilegjet q\u00eb ofrojm\u00eb p\u00ebr klient\u00ebt tan\u00eb t\u00eb rinj t\u00eb web-hosting.<\/a>N\u00eb nj\u00eb zgjidhje enterprise, kopjimi rezerv\u00eb i instalimit ndodh me nj\u00eb num\u00ebr nodash t\u00eb dedikuar t\u00eb klasterit. N\u00eb k\u00ebt\u00eb rast, p\u00ebr shembull, Commvault funksionon vet\u00ebm me nj\u00eb klaster me dy node, n\u00eb t\u00eb cilin Primary dhe Secondary jan\u00eb ngusht\u00ebsisht t\u00eb lidhura me nodat specifike. Dhe ka kuptim t\u00eb b\u00ebsh backup vet\u00ebm me Primary, sepse backup nga Secondary ka kufizimet e veta. P\u00ebr shkak t\u00eb ve\u00e7orive t\u00eb DBMS, dump n\u00eb Secondary nuk krijohet, dhe k\u00ebshtu mbetet vet\u00ebm mund\u00ebsia e backup-it t\u00eb skedar\u00ebve.<\/p>\n

P\u00ebr t\u00eb zvog\u00ebluar rreziqet e pezullimit, kur krijohet nj\u00eb sistem q\u00ebndres\u00eb, formohet nj\u00eb konfiguracion klasteri \"i gjall\u00eb\", dhe Primary mund t\u00eb migroj\u00eb gradualisht mes server\u00ebve t\u00eb ndrysh\u00ebm. P\u00ebr shembull, softueri Patroni (n\u00eb anglisht, 'Patroni') e aktivizon automatikisht Primary n\u00eb nj\u00eb nod t\u00eb zgjedhur rast\u00ebsisht t\u00eb klasterit. SRK nuk ka nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb ndjekur k\u00ebt\u00eb \"nga kuti\", dhe n\u00ebse konfigurimi ndryshon, proceset d\u00ebshtojn\u00eb. K\u00ebshtu, implementimi i menaxhimit t\u00eb jasht\u00ebm pengon SRK-n\u00eb t\u00eb funksionoj\u00eb n\u00eb m\u00ebnyr\u00eb efektive, sepse serveri menaxhues thjesht nuk kupton se nga cili dhe cilat t\u00eb dh\u00ebna duhet t\u00eb kopjoj\u00eb.<\/p>\n

Nj\u00eb tjet\u00ebr problem \u00ebsht\u00eb realizimi i backup-it n\u00eb Postgres. Ajo \u00ebsht\u00eb e mundur p\u00ebrmes dump, dhe n\u00eb bazat e vogla funksionon. Por n\u00eb bazat e m\u00ebdha, dump b\u00ebhet ngadal\u00eb, k\u00ebrkon shum\u00eb burime dhe mund t\u00eb shkaktoj\u00eb d\u00ebshtimin e ekzemplarit t\u00eb DB.<\/p>\n

Backup-i i skedar\u00ebve e korrigjon situat\u00ebn, por n\u00eb bazat e m\u00ebdha shkon ngadal\u00eb, sepse punon n\u00eb modalitetin nj\u00ebkanal\u00ebsh. Po ashtu, ofruesit kan\u00eb nj\u00eb s\u00ebr\u00eb kufizimesh t\u00eb tjera. Ndonj\u00ebher\u00eb nuk mund t\u00eb p\u00ebrdoren p\u00ebr nj\u00ebkoh\u00ebsisht backup-i i skedar\u00ebve dhe dump-i, ndonj\u00ebher\u00eb nuk mb\u00ebshtetet deduplication. Problemet jan\u00eb t\u00eb shumta, dhe shpesh m\u00eb e leht\u00eb \u00ebsht\u00eb t\u00eb zgjidhni nj\u00eb DBMS t\u00eb shtrenjt\u00eb, por t\u00eb provuar n\u00eb vend t\u00eb Postgres.<\/p>\n

Nuk ka ku t\u00eb t\u00ebrhiqemi! Prapa nesh \u00ebsht\u00eb Moska me zhvilluesit!<\/p>\n

Megjithat\u00eb, s\u00eb fundmi ekipi yn\u00eb u p\u00ebrball me nj\u00eb sfid\u00eb t\u00eb v\u00ebshtir\u00eb: n\u00eb projektin e krijimit t\u00eb AIS OSAGO 2.0, ku ne krijuam infrastrukturen IT, zhvilluesit p\u00ebr sistemin e ri zgjodh\u00ebn PostgreSQL.<\/h2>\n

\nZhvilluesit e m\u00ebdhenj t\u00eb softuerit e kan\u00eb shum\u00eb m\u00eb t\u00eb leht\u00eb t\u00eb p\u00ebrdorin zgjidhje \"trending\" open-source. N\u00eb stafin e Facebook-ut ka mjaft specialist\u00eb q\u00eb mb\u00ebshtesin funksionimin e k\u00ebsaj DBMS. Nd\u00ebrsa n\u00eb rastin e RSA, t\u00eb gjitha detyrat e \"dit\u00ebs s\u00eb dyt\u00eb\" bien mbi supet tona. Na u k\u00ebrkua t\u00eb sigurojm\u00eb q\u00ebndrueshm\u00ebrin\u00eb, t\u00eb krijojm\u00eb nj\u00eb klaster dhe, natyrisht, t\u00eb vendosim kopjimin rezerv\u00eb. Logjika e veprimeve ishte k\u00ebshtu: <\/p>\n

T\u00eb m\u00ebsojm\u00eb SRK-n\u00eb t\u00eb b\u00ebj\u00eb backup nga nodi Primary i klasterit. P\u00ebr k\u00ebt\u00eb, SRK duhet ta gjej\u00eb at\u00eb \u2014 dmth, \u00ebsht\u00eb e nevojshme integrimi me ndonj\u00eb zgjidhje p\u00ebr menaxhimin e klasterit PostgreSQL. N\u00eb rastin e RSA p\u00ebrdorej softueri Patroni. <\/p>\n