So, keep this in mind when planning your Exchange LUNs in conjunction with the backup solution to be used. Then, after restoring the database, you can start replaying log files. With the database and log files on separate LUNs, you can restore the database LUN, which leaves the LUN with the log files intact. By definition, you can now only restore the database and log files as they were on Saturday 6:00 log files which were created after Saturday 6:00 are lost.
SHADOW ERA DUPLICATE ITEMS FULL
So, changes (log files) made after the snapshot are lost and you have no point-in-time recovery options.įor example, with the database and log files on a single LUN, suppose you create a full backup on Saturday 6:00. This restricts your recovery options, since you can by definition only restore that complete LUN, overwriting log files created after taking the snapshot. Therefor, if you put the Exchange database and log files on a single LUN, it will always create a snapshot of the whole LUN. The reason for this requirement is that hardware VSS solutions operate at the hardware level, i.e. To deploy a LUN architecture that only uses a single LUN per database, you must have a database availability group (DAG) that has two or more copies, and not be using a hardware-based Volume Shadow Copy Service (VSS) solution. I had a question why you need to design seperate LUNs for Exchange database and log files when using a hardware based Volume Shadow Copy Service (VSS) backup solution, as mentioned in this TechNet article:
0 kommentar(er)
