topic Re: Snapshot clones - one is read only, another is not? in Array Performance and Data Protection

Snapshot clones - one is read only, another is not?

nick090971 — Tue, 01 Sep 2015 17:01:44 GMT

I have two physical Windows 2012 servers with data drives that are getting snapshots. One is just a file server and does not use any snapshot synchronization. The other is a SQL server that does synchronize.

If I go to the volume on the file server, select a snapshot, clone it and then mount it I can read and write to that volume.
If I do the same on the SQL server, select one of its snapshots, clone it and mount it, the volume is mounted read-only.

Is this expected? Why is the SQL volume read only when the file server volume is r/w but I follow the same steps cloning the snapshot? Is there a way to see in the Nimble interface if a volume is read-only, or is this flag on the OS level somewhere? I would really like to be able to mount the SQL volumes with r/w so we can use them as dev instances of the data if needed.

Re: Snapshot clones - one is read only, another is not?

chris24 — Wed, 02 Sep 2015 07:31:28 GMT

Hello this is due to the OS, to clear the flag read only flags from the volume / disk.

diskpart

list disk

select disk x

attributes disk clear readonly

select volume x

detail volume

attributes volume clear readonly

attributes volume clear hidden

attributes volume clear shadowcopy

Re: Snapshot clones - one is read only, another is not?

Nick_Dyer — Wed, 02 Sep 2015 08:53:25 GMT

You can also use the new mounting tools within Nimble Windows Toolkit 2.3 to assist with the re-signaturing and clearing of read only within Diskpart should you want to. Here's Julian Cates's blog on the feature: Nimble OS 2.3 - Restore Workflow Automation for Snapshots