I never said refresh taking 2 days ....when did i say that ?
Standby UAT database is used for testing multiple things and also for
fetching some reports along with if performance testing if required in any
way.
On Fri, Nov 15, 2019 at 5:51 AM Mladen Gogala <gogala.mladen@xxxxxxxxx>
wrote:
Also, why is the refresh taking 2 days? Storage snapshot is a known and
tried technology which shouldn't be a problem to script. I know of several
backup products which can directly utilize storage snapshots (Delphix,
Commvault, Veeam, Rubrik). Even the dinosaurs like NetBackup or DD Boost
can be scripted to utilize storage snapshots. It takes 7 days to create and
populate a whole planet and database refresh should take less than 2 days,
even if you encounter a talking snake.
On 11/14/19 7:55 AM, Clay Jackson (cjackson) wrote:
So, as I understand the problem statement; you have a UAT database,
protected by DataGuard, that gets periodically refreshed from a Production
database, and the refresh takes 2 days.
So, when you do your refresh, why not stop DataGuard before the refresh;
and refresh both the primary and “standby” at the same time. More work;
but shouldn’t take significantly more time.
Sent from my iPhone
Clay Jackson
On Nov 14, 2019, at 4:56 AM, Noveljic Nenad <nenad.noveljic@xxxxxxxxxxxx>
<nenad.noveljic@xxxxxxxxxxxx> wrote:
CAUTION: This email originated from outside of the organization. Do not
follow guidance, click links, or open attachments unless you recognize the
sender and know the content is safe.
That's true - also non-production databases can have stricter recovery
point and time objectives. However, copy-on-write snapshots seem like a
better fit for the case you described - especially for large databases.
Best regards,
Nenad
https://nenadnoveljic.com/blog/
<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnenadnoveljic.com%2Fblog%2F&data=02%7C01%7Cclay.jackson%40quest.com%7C0c0eaa3c1cc84e39e7d508d768e8ef92%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637093221973691129&sdata=Ey7%2BsRF90CT%2FJ0KgPsyeTjNyt2ZGD%2B9wZspaeufwkDk%3D&reserved=0>
*From:* Mark W. Farnham <mwf@xxxxxxxx> <mwf@xxxxxxxx>
*Sent:* Donnerstag, 14. November 2019 00:01
*To:* howard.latham@xxxxxxxxx; Noveljic Nenad
<nenad.noveljic@xxxxxxxxxxxx> <nenad.noveljic@xxxxxxxxxxxx>
*Cc:* rjgoulet@xxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
*Subject:* RE: is there any way i can avoid rebuild physical standby
database after every PROD to UAT database refresh ?
Also hang on a minute about whether the standby of UAT is needed.
Can the UAT be reinstantiated from PROD? Yes. So recovery to the point of
a fresh refresh from PROD does not require a backup.
However before you run off shouting a standby is not needed you need to
know how UAT is used.
For example, it could be refreshed once a week or month and used to test
development that has been passed out from engineering. The first step
after the refresh might be complicated changes to the structure of the data
that may require hours or days. Let’s say that is cleverly scheduled for
the weekend, and then the UAT test team commences work on the clean update
massaged from PROD to use the improved application suite.
Bam! the primary UAT server bites it. Do the thousands of dollars per hour
expert user new functionality testers (often including consultants) twiddle
their thumbs for a couple days while UAT is restored from PROD and then
re-updated to be ready to test the software revision? NO, because you bring
up the standby and fork them over there until you can fail back.
Now, given the exact purpose and use of the UAT database at a particular
department of a particular company, perhaps we can streamline something.
The large majority of UAT databases I have seen are used for three things:
1) the scenario above, testing new application functionality
2) vendor updates (Oracle RDBMS, operating system, or both) where you
refresh from PROD, run the updates (or patches), and then run your
regression test. The updates and patches can be too long to repeat cost
effectively.
3) experimenting on the PROD data’s copy on UAT to investigate User
reported bugs.
Having this functionality unavailable during whatever prime time is while
a new refresh is done is often not acceptable. In 24 by 7 nearly flat
loads, it may require 2 UAT databases, each with a standby, so that while
one is being refreshed the other is still available for anything that does
not require newer data.
Question it? Sure. But there is a very good chance it IS needed.
mwf
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee
you should in particular not disseminate, distribute, modify or copy this
e-mail. Please notify the sender immediately by e-mail, if you have
received this message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which
shall prevail in any case, we take it as your authorization to correspond
with you by e-mail if you send us messages by e-mail. However, we reserve
the right not to execute orders and instructions transmitted by e-mail at
any time and without further explanation.
E-mail transmission may not be secure or error-free as information could
be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of
Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively
referred to as "Vontobel Group") for any damages resulting from e-mail use
is excluded. You are advised that urgent and time sensitive messages should
not be sent by e-mail and if verification is required please request a
printed version.
Please note that all e-mail communications to and from the Vontobel Group
are subject to electronic storage and review by Vontobel Group. Unless
stated to the contrary and without prejudice to any contractual agreements
between you and Vontobel Group which shall prevail in any case,
e-mail-communication is for informational purposes only and is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction.
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your
consent to forward you commercial communications. You can exercise, at any
time and under the terms established under current regulation, your rights.
If you prefer not to receive any further communications, please contact
your client relationship manager if you are a client of Vontobel Group or
notify the sender. Please note for an exact reference to the affected group
entity the corporate e-mail signature. For further information about data
privacy at Vontobel Group please consult www.vontobel.com
<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.vontobel.com&data=02%7C01%7Cclay.jackson%40quest.com%7C0c0eaa3c1cc84e39e7d508d768e8ef92%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637093221973691129&sdata=Jyj8PEJ29MrVpUydAhXJvuArcsH3o%2BPREhhjzG49m64%3D&reserved=0>
.
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
