External dump after "quiesce" and "dump cumulative"

[Former Member]

Hello Experts,
Suppose, I have a production database P01 and I run the
following backup strategy:
1. Every night at 02:00, I run a „dump database P01 to … “.
2. Every 6 hours (at 08:00, 14:00 and 20:00) I run a “dump
database P01 cumulative to . . .”.
As the result every day, I have a full DB dump and three
cumulative dumps each based on the last full dump executed
on the same day at 02:00.
The first cumulative dump includes all changes made on the
same day between 02:00 and 08:00, the second one – all
changes, made to the DB between 02:00 and 14:00, and the
third one – all changes, made in the time 02:00 and 20:00
on the same day.
Now I would like to use the possibility to run “external”
dumps.
I would like to run the following procedure at 02:00:
1. Execute “quiesce database . . . hold P01 for external
dump“.
2. Run an external dump / copy the devices using the storage
tools.
3. Execute „quiesce database . . . release“.
The question is, what will be the behavior of the cumulative
dump, for instance the one I will then execute at 08:00 ?
Will this cumulative dump be based on the DB state at the
execution of the “quiesce database . . . hold P01 for external
dump“ command ?
Or will ASE ignore the execution of the external dump and
base the cumulative dump on the last executed full DB dump:
„dump database P01 to … “ ?
Regards

[Former Member]

Thank you, the idea to run tests - I also think the tests will be the best check. Will do.

Actually I also think, the command: “quiesce database ... for external dump“ will not affect the full/cumulative dump series.

Unfortunately my goal is to execute such an external backup, which will do affect. The question is – how can I run such one?

If such external backup do not affect the starting point of the next cumulative one, then we cannot actually combine the external full and conventional cumulative.

Will mean, the cumulative backup will grow unlimited as the starting point will be the same all the time until we will run the next conventional full backup of the database.