Hello Dirk,

sorry for being late with my comments on NDMP backups. In my opinion some
of the stuff regarding reporting and administration is admittedly still
rather odd:

- the full backup will be kept until the next one is performed, but it will
no longer be reported on with the query, so don´t worry if it doesn´t seem
to show up... you can´t prove it is still there apart from performing a
restore:  hard to believe, I admit, but it just works that way
- backups are processes and reported as such, not as sessions
- the summary table reports processes on volumes but utterly fails to
report on virtual filespacemappings regarding these processes, making it
useless for reporting and analysis

so just to have fun, start your backups of vfsmappings per admin script in
parallel/sequential according to your ressources and try to find which was
which... The only place I have found so far is in the actlog and I am
rather reluctant to script something which has to be maintained manually.

Finding the right frequency regarding full/differential is a pain, we have
come up with a 4-week rotation using virtual filespace-mappings which works
quite well as only approximately a quarter of the data goes through a full
per weekend.
So we end up with one admin schedule and script for Monday through
Wednesday doing differentials plus four for the four fridays doing partial
fulls.

I asked about the missing reporting granularities for vfsmappings in
Oxford, but didn´t come up with a product capable of doing this
out-of-the-box to this extend at the moment (come on, would be a great
feature and fun to build).

Not to get a wrong impression: I´m quite happy with NDMP as a neat way to
provide for secondary disaster recovery for large filers where single file
restore is not the focus: it is scalable, stable and, in certain
boundaries, performs decently.

Regards,
Markus


--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
______________________________________________________________________

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.