I started using the Windows snapshot scripts for our EC2 instances and while it seemed to make sense initially, the more I look into how diskshadow.exe works, the less I'm convinced.
As I understand it, issuing a "create" command with diskshadow does create a shadow copy of the volumes specified by "add volume X:", but the consistent shadow drive is actually another device that needs to be exposed.
It's not as if writes to the C: volume, are being diverted to another hidden drive and then merged back after the backup is done.
So after "create" and "begin backup" are issued, if I still write something to the volumes I think I wouldn't have any more consistency guarantees than if I hadn't issued those commands (since the consistent/shadow data is hidden in another unexposed drive)
What do you think? Do you have any documentation that would say otherwise?
Hi,
I started using the Windows snapshot scripts for our EC2 instances and while it seemed to make sense initially, the more I look into how diskshadow.exe works, the less I'm convinced.
As I understand it, issuing a "create" command with diskshadow does create a shadow copy of the volumes specified by "add volume X:", but the consistent shadow drive is actually another device that needs to be exposed.
It's not as if writes to the C: volume, are being diverted to another hidden drive and then merged back after the backup is done.
So after "create" and "begin backup" are issued, if I still write something to the volumes I think I wouldn't have any more consistency guarantees than if I hadn't issued those commands (since the consistent/shadow data is hidden in another unexposed drive)
What do you think? Do you have any documentation that would say otherwise?