<div>
It definitely depends on the situation. &nbsp;Most of the places I have been the non-production databases were just copies of production anyway. &nbsp;There wasn't anything special in them.<br />
<br />
If the QA team had a baseline that they needed, we made sure that was in an export file so we could easily put it back to their known good state. &nbsp;So, special backups of their environments were not necessary as they only care about the known good state. &nbsp;Plus we did not want to have to do a full restore just for their small set of test data.<br />
<br />
If we had an issue with a non-production database, we would just restore production over it. &nbsp;Takes the same amount of time as restoring a backup of the test database. &nbsp;Development might lose some structure changes, but with good change management, you just re-apply everything.
</div>


It definitely depends on the situation.  Most of the places I have been the non-production databases were just copies of production anyway.  There wasn't anything special in them.

If the QA team had a baseline that they needed, we made sure that was in an export file so we could easily put it back to their known good state.  So, special backups of their environments were not necessary as they only care about the known good state.  Plus we did not want to have to do a full restore just for their small set of test data.

If we had an issue with a non-production database, we would just restore production over it.  Takes the same amount of time as restoring a backup of the test database.  Development might lose some structure changes, but with good change management, you just re-apply everything.

<div>
<div class="content wysiwyg-content">
For each business applicaiton with an underlying database, we seem to have a live production database, a test database (with test clone of the app), and also a user acceptance database for changes/upgrades. our admins only seem to backup the live production db. is this common? Or can there be instances whereby you also backup your test and uat databases as well?
</div>
</div>


For each business applicaiton with an underlying database, we seem to have a live production database, a test database (with test clone of the app), and also a user acceptance database for changes/upgrades. our admins only seem to backup the live production db. is this common? Or can there be instances whereby you also backup your test and uat databases as well?

test and uat database backups

Oracle is an object-relational database management system. It supports a large number of languages and application development frameworks. Its primary languages are SQL, PL/SQL and Java, but it also includes support for C and C++. Oracle also has its own enterprise modules and application server software.

Oracle Database

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.