Subject | NBackup doubts |
---|---|
Author | Alexandre Benson Smith |
Post date | 2009-06-15T00:23:10Z |
Hi !
I will use NBackup for the first time in production FB CS 2.1.2
(Firebird TCP/IP server version LI-V2.1.2.18118 Firebird 2.1).
First Question:
I have read in the past some problems with NBackup (even corrupting
databases), I took a look on tracker and see some tickets marked as
fixed, the tickets marked as Open/Unresolved are improvements, I just
like to confirm that the current version of NBackup doesn't have any
known issues.
Second Question:
I plan to have:
Level 0 Monthly (every 1st day of the month)
Level 1 Weekly (every Sunday)
Level 2 Daily (everyday at midnight)
Level 3 Hourly (every hour of course :) )
I will run it trough bash scripts using cron and , I was in doubt with
this kind of situations:
What would happen when two NBackup's task run at the same time or when a
task run during the execution of another one, examples:
July, 1st at midnight would start the Monthly backup, and let suppose
this day is a Sunday, so at the very same time the Level 0 and Level 1
would run in parallel, there is any problem with this scenario ?
The other case, the Daily task started at midnight and did not finished
until 1:00AM when the hourly task would start, how does the 2 back-up
files would be related ? The hourly back-up would be an incremental of
the daily backup of the day before ?
I tried to force those situations and got:
[
PROBLEM ON "begin backup".
unsuccessful metadata update
-Database is already in the physical backup mode
SQLCODE:-607
]
Failure: Database error
As far as I can see, the hourly job was just aborted because the daily
job was executing, can I safely ignore such error ? (With "safely" I
meant to treat the error at my bash script)
The last one:
Here is a sentence from Release Notes
"6. Add a record of this backup operation to RDB$BACKUP_HISTORY. Record
current level, SCN, snapshot
GUID and some miscellaneous stuff for user consumption."
I did a select on this table and it's empty, so I presumed that the
record is deleted after the end of the back-up cycle, did a test
querying it while the back-up is running, but still see no records, any
comments about this ?
Sorry if those are newbie questions, but I don't remember to have read
something about this and didn't read anything related on Release Notes
or NBackup manual.
I just want to be sure, I am a bit paranoic regarding back-ups.
TIA
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br
I will use NBackup for the first time in production FB CS 2.1.2
(Firebird TCP/IP server version LI-V2.1.2.18118 Firebird 2.1).
First Question:
I have read in the past some problems with NBackup (even corrupting
databases), I took a look on tracker and see some tickets marked as
fixed, the tickets marked as Open/Unresolved are improvements, I just
like to confirm that the current version of NBackup doesn't have any
known issues.
Second Question:
I plan to have:
Level 0 Monthly (every 1st day of the month)
Level 1 Weekly (every Sunday)
Level 2 Daily (everyday at midnight)
Level 3 Hourly (every hour of course :) )
I will run it trough bash scripts using cron and , I was in doubt with
this kind of situations:
What would happen when two NBackup's task run at the same time or when a
task run during the execution of another one, examples:
July, 1st at midnight would start the Monthly backup, and let suppose
this day is a Sunday, so at the very same time the Level 0 and Level 1
would run in parallel, there is any problem with this scenario ?
The other case, the Daily task started at midnight and did not finished
until 1:00AM when the hourly task would start, how does the 2 back-up
files would be related ? The hourly back-up would be an incremental of
the daily backup of the day before ?
I tried to force those situations and got:
[
PROBLEM ON "begin backup".
unsuccessful metadata update
-Database is already in the physical backup mode
SQLCODE:-607
]
Failure: Database error
As far as I can see, the hourly job was just aborted because the daily
job was executing, can I safely ignore such error ? (With "safely" I
meant to treat the error at my bash script)
The last one:
Here is a sentence from Release Notes
"6. Add a record of this backup operation to RDB$BACKUP_HISTORY. Record
current level, SCN, snapshot
GUID and some miscellaneous stuff for user consumption."
I did a select on this table and it's empty, so I presumed that the
record is deleted after the end of the back-up cycle, did a test
querying it while the back-up is running, but still see no records, any
comments about this ?
Sorry if those are newbie questions, but I don't remember to have read
something about this and didn't read anything related on Release Notes
or NBackup manual.
I just want to be sure, I am a bit paranoic regarding back-ups.
TIA
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br