Instant recovery VM with SQL server and logs

[petr.svab@coma.cz]

Hi,
I need run Instant VM recovery with installed SQL server, but before access VM I need use all SQL logs created after last image backup.
Is it possible?
...or may be new feature request?

Petr Svab

[PetrM]

Hi Petr and Welcome to Veeam R&D Forums!

Would you be so kind to clarify what is the purpose to use SQL logs before Instant Recovery? Not sure that I've got your use case but you may run database PIT restore using Veeam Explorer for Microsoft SQL.

Thanks!

[petr.svab@coma.cz]

No, it is not same. Because restore SQL database by Explorer means copying all the data again. This is useful for restore corrupted database. But I talking about corrupted whole VM. The database I already have in VM - but without last logs. This copying may take additional hours. First I copying VM as backup (system with database) and second I copying database (restore database by explorer). In backup VM I have database but I miss the last logs.
P.

[PetrM]

Still not sure that I have enough clarity. May I ask you to elaborate on:
1. What problem are you trying to solve?
2. What do you mean by "use all SQL logs created after last image backup" ? In particular, how are you going to use these logs?

Thanks!

[petr.svab@coma.cz]

I try describe it.
I have backups:
12:00 backup VM (vbk/vbi
12:10 log backup (vbl)
12:20 log backup (vbl)
12:25 disaster VM
I want make instant VM recovery with all backuped data - to 12:20 state (or optionally to 12:10)
It's clear?

[PetrM]

Hi Petr,

Yes, thanks. Well, you can restore the entire VM or run Instant Recovery of the VM to the point in time of 12:00. After that, you can restore database to the latest state of 12:20 using Veeam Explorer for Microsoft SQL.

Thanks!

[petr.svab@coma.cz]

Yes, but effect instant recovery is out, because I need restore whole database, what can be in hours.
My idea is include logs to database, which is in VM. Without long restore.
....and I am not sure if I can restore database by explorer from backup, if this backup run by instant VM recovery.

[PetrM]

If you need to bring database online ASAP, then you may run Instant Database Recovery. The possibility to recover a database using transaction log backups only is an existing feature request for our future releases. And answering your last question about the usage of the same backup: you can run any restore activity including Entire VM restore or Instant VM Recovery and trigger restore by Explorer from the same backup simultaneously.

Thanks!

[petr.svab@coma.cz]

Instant Database Recovery is good feature for corrupted database only.
I talked about case, when id corrupted VM.
If you have this solution as feature request, I will be looking forward to it.

[mcz]

Hi Petr,

I've discussed the same situation on the community hub and I think I do exactly understand what you're asking for... Have a look here:

https://community.veeam.com/discussion- ... #post22509

Long story short: You first do a instant recovery of the vm, then you'd delete the existing database and then you start a instant database recovery

[Link State]

true story mcz

[petr.svab@coma.cz]

Michael,
you are right, understand this solving.
But...why not exists method, where I choose transaction log for join into exists database in VM backup?
or, is some possibility, how can I get logs from vlb container?

[mcz]

Well Petr, I'd love to have such a feature too. But so far I'm not aware of any other "hacks" then the mentioned ones. You have to use the wizards...

[petr.svab@coma.cz]

Yes, I am aware of. But very usable feature request, not impossible, is the following scenario:
1. start VM Instant recovery without network
2. implement vlb to database
3. allow network

[mcz]

yeah but you need a network connection for the rollforward. Otherwise it isn't trivial...

[petr.svab@coma.cz]

And how does IDR work? For finally database state with last logs I don't need working VM with DB server, isn't it?
...or I missed?

[PetrM]

Hello,

It's up to you whether to restore a VM and restore database on it or to restore DB to the original server or to another server. There is no option to extract logs from the .vlb container. Anyway, the request is clear including an idea of network-less restore. Your feedback is highly appreciated, but I cannot provide any info regarding ETA as it depends on many different factors, for instance on the priorities of other requests and on the complexity of implementation.

Thanks!