Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Ingres Topics / June 2005

Tip: Looking for answers? Try searching our database.

Safe online transportable backups

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Emiliano - 21 Jun 2005 12:10 GMT
Is there a procedure to create safe, transportable online backups? I
don't need cross-platform transportability (we're windows-only), but I
do need a backup snapshot that can easily be loaded in another Ingres
installation easily without much user interaction.

Checkpoints appear to be highly machine-bound and what little I've
been able to find about transporting these it appears to be a
check-these-1000-things-edit-these-100-files-DONT-DO-... procedure
that we just can't deploy to our customers.

CopyDB would seem to be the best fit for our needs but I'm worried
about existing connections (online backup!) altering data while it is
being copied out.

would altering the copy.out script to first take read locks on all
tables be a safe way to go? Any other way that I'm missing?

Signature

Emiliano

Rainman - 22 Jun 2005 02:15 GMT
Would the xml import/export of R3 be of use? It looks like a possible
option for other migrations?

Good luck! Keep everyone posted!!

> Is there a procedure to create safe, transportable online backups? I
> don't need cross-platform transportability (we're windows-only), but I
[quoted text clipped - 12 lines]
> would altering the copy.out script to first take read locks on all
> tables be a safe way to go? Any other way that I'm missing?
Emiliano - 22 Jun 2005 14:53 GMT
> Would the xml import/export of R3 be of use? It looks like a possible
> option for other migrations?

It's an interesting option, but the manual doesn't state anything
whatsoever about locking, and the exported metadata is incomplete --
no rules, no SPs, no constraints... I'm hoping that a modified
copy.out will do the job. I've taken out the autocommit and the
readlock = nolock, did an 'select * from <table>' for all tables, then
the usual copy statements, then an explicit commit. I've sent it to CA
for evaluation, I'll let you know.

Signature

Emiliano

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.