Permissions as in the permissions on the user account to access the actual database, in MySQL these are stored in separate system tables, don't know where or how PG stores that information. OTRS permissions are stored in the OTRS tables, so they will be backed up/restored.
On 10 June 2013 16:41, Paul Simons <[email protected]> wrote: > Hum nice idea for the attachments - I'll look closely at that. > Could you expand on your 'permissions' - which permissions - I thought they > were restored from the SQL file. > Regards > > ___________________________________________ > Paul Simons > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Steven Carr > Sent: Monday, June 10, 2013 5:25 PM > To: User questions and discussions about OTRS. > Subject: Re: [otrs] Backup and Restore pearl script - success? failure? > > Not used Postgres but with MySQL you need to prep the environment for the > database i.e. create the user and database and assign permissions. > Then the restore will create all the tables and restore the data. > > Can't say I've ever liked the idea of an "all in one" backup/restore script. > I have MySQL backups nightly with transaction logs every 6 hours so can roll > the database back/forward to when needed and I take snapshot backups of the > /opt/otrs filesystem to be able to restore. > For ease of management we store the attachments in the database. > > Steve > > > > On 10 June 2013 16:10, Paul Simons <[email protected]> wrote: >> Has anybody successfully used the 'backup.pl' and 'restore.pl'? >> If so what preparation did you do before running the scripts? >> - new PostgreSQL database? >> - from template 0? >> - load schema before >> - create user, role? >> - etc >> >> The documentation is a little light on the preceding steps Regard >> >> ___________________________________________ >> Paul Simons >> >> ________________________________ >> >> Disclaimer: This e-mail (and any attachments to it) is confidential and >> intended solely for the named person/s to whom it is addressed. If you are >> not an intended recipient, please notify us immediately and delete the email >> from your system. Any review, dissemination or other use of it in these >> circumstances is prohibited. >> --------------------------------------------------------------------- >> OTRS mailing list: otrs - Webpage: http://otrs.org/ >> Archive: http://lists.otrs.org/pipermail/otrs >> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs > > ________________________________ > > Disclaimer: This e-mail (and any attachments to it) is confidential and > intended solely for the named person/s to whom it is addressed. If you are > not an intended recipient, please notify us immediately and delete the email > from your system. Any review, dissemination or other use of it in these > circumstances is prohibited. > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
