July 24, 2017 at 3:04 pm
I am not DBA person and need to back from production and restore to UAT and I have some understanding issue here as my colleague says Production server is backed up everyday(differential). So he need not do back up again to restore to UAT. Normally ,i take backup file and restore file to UAT. But he says " he copied prod to uat and restored on top of it?". Can anyone explain how that works?
July 25, 2017 at 4:07 am
if the dba already has a backup chain then you need to ask them to provide all the files including the full backup to be able to restore the database to another environment
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 25, 2017 at 5:35 am
komal145 - Monday, July 24, 2017 3:04 PMBut he says " he copied prod to uat and restored on top of it?". Can anyone explain how that works?
Without being there, this is a total guess. I imagine that what the DBA has said to you though is that the copied the Backup files to your UAT environment, and then restored that backup on UAT and replaced the existing copy you had.
Doing back ups of a database outside of a DBA's chain could have knock-on effects you don't want. Say, for example, the Database is backed up at 03:00 every day, and a transaction log every 5 minutes. A "user" then comes along and creates a backup at 09:17:37 and sends it to their local share or PC. They do their restore, but as the back up is quite large, they delete it afterwards . The server then encounters some problem at 23:46:17. The DBA goes to restore the database to a point in time a little before the problem (say 23:40:00). They start running the transaction files, and then it falls over at 09:20:00. That's because a back-up was taken between and those further files are useless to the DBA without the backup taken at 09:17:37. End result: 14 hours of data is lost.
If you aren't responsible for managing the Backups, or don't know how they work, leave them be. If you need a copy, get someone else to do it for you who knows what they are doing.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
July 25, 2017 at 10:13 am
Thom A - Tuesday, July 25, 2017 5:35 AMkomal145 - Monday, July 24, 2017 3:04 PMBut he says " he copied prod to uat and restored on top of it?". Can anyone explain how that works?Without being there, this is a total guess. I imagine that what the DBA has said to you though is that the copied the Backup files to your UAT environment, and then restored that backup on UAT and replaced the existing copy you had.
Doing back ups of a database outside of a DBA's chain could have knock-on effects you don't want. Say, for example, the Database is backed up at 03:00 every day, and a transaction log every 5 minutes. A "user" then comes along and creates a backup at 09:17:37 and sends it to their local share or PC. They do their restore, but as the back up is quite large, they delete it afterwards . The server then encounters some problem at 23:46:17. The DBA goes to restore the database to a point in time a little before the problem (say 23:40:00). They start running the transaction files, and then it falls over at 09:20:00. That's because a back-up was taken between and those further files are useless to the DBA without the backup taken at 09:17:37. End result: 14 hours of data is lost.
If you aren't responsible for managing the Backups, or don't know how they work, leave them be. If you need a copy, get someone else to do it for you who knows what they are doing.
Thank you so much for explanation. I have been learning new stuff from this group and very useful.
July 26, 2017 at 6:22 am
Thom A - Tuesday, July 25, 2017 5:35 AMDoing back ups of a database outside of a DBA's chain could have knock-on effects you don't want. Say, for example, the Database is backed up at 03:00 every day, and a transaction log every 5 minutes. A "user" then comes along and creates a backup at 09:17:37 and sends it to their local share or PC. They do their restore, but as the back up is quite large, they delete it afterwards . The server then encounters some problem at 23:46:17. The DBA goes to restore the database to a point in time a little before the problem (say 23:40:00). They start running the transaction files, and then it falls over at 09:20:00. That's because a back-up was taken between and those further files are useless to the DBA without the backup taken at 09:17:37. End result: 14 hours of data is lost.If you aren't responsible for managing the Backups, or don't know how they work, leave them be. If you need a copy, get someone else to do it for you who knows what they are doing.
To be clear, full and diff backups do not break the log chain
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 27, 2017 at 11:25 am
In addition, A differential backup is based on the most recent, previous full data backup. A differential backup captures only the data that has changed since that full backup. The full backup upon which a differential backup is based is known as the base of the differential.
Best regards
July 28, 2017 at 6:45 am
Thanks for the reply)
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply