BRRABill's Field Report With XenServer
-
The snapshot (from what I can see) allocates the exact same amount of space.
So if the virtual disk is allocated 100GB, the snapshot will also be allocated 100GB.
-
@Dashrender said:
Well - what does allocated mean to you? It means in use.
Though I've seen allocated to mean - I have allocated this VHD to 1 TB, though when setup with Thin Provisioning.. it will only grow as things push it into actual needed space. As mentioned previously it won't shrink (at least not on it's own) when things are deleted from the filesystem inside the VHD. So in that case allocated means max usable, even though it's not what's currently in use.
Snaps are not part of that pool, though.
-
Not part of what pool?
Here it's showing everything together.
-
Snaps are not part of the "amount I intended to allocated with the main disks." Snaps are extra on top of that.
-
@scottalanmiller said:
Snaps are not part of the "amount I intended to allocated with the main disks." Snaps are extra on top of that.
Then why list it in the allocated pool?
-
@Dashrender said:
@scottalanmiller said:
Snaps are not part of the "amount I intended to allocated with the main disks." Snaps are extra on top of that.
Then why list it in the allocated pool?
Because it IS allocated and using space. It has to be shown.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
Snaps are not part of the "amount I intended to allocated with the main disks." Snaps are extra on top of that.
Then why list it in the allocated pool?
Because it IS allocated and using space. It has to be shown.
where is it using 700 GB? it can't be - I simply don't have 700 for it to be using.
-
@Dashrender said:
where is it using 700 GB? it can't be - I simply don't have 700 for it to be using.
That's the max size it could ever be. A duplicate of the amount for the drive it is snapshotting. (Is that a word?)
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
Snaps are not part of the "amount I intended to allocated with the main disks." Snaps are extra on top of that.
Then why list it in the allocated pool?
Because it IS allocated and using space. It has to be shown.
where is it using 700 GB? it can't be - I simply don't have 700 for it to be using.
It's not, that's thin provisioning, isn't it?
-
@BRRABill said:
@Dashrender said:
where is it using 700 GB? it can't be - I simply don't have 700 for it to be using.
That's the max size it could ever be. A duplicate of the amount for the drive it is snapshotting. (Is that a word?)
Yes
-
Both yes, that is what you are seeing and yes, that is a word.
-
@scottalanmiller said:
@BRRABill said:
@Dashrender said:
where is it using 700 GB? it can't be - I simply don't have 700 for it to be using.
That's the max size it could ever be. A duplicate of the amount for the drive it is snapshotting. (Is that a word?)
Yes
I used the layman terms. Because I am, well, you know...
-
Does XS support reclaiming/compacting space in a virtual disk?
I know it says it does not support shrinking a virtual disk, but can you reclaim (compact) that space?
-
@BRRABill said:
Does XS support reclaiming/compacting space in a virtual disk?
I know it says it does not support shrinking a virtual disk, but can you reclaim (compact) that space?
am I mising something? Isn't shrinking the same as reclaiming?
-
@Dashrender said:
am I mising something? Isn't shrinking the same as reclaiming?
I don't think so, but I could be wrong.
Reclaiming is adjusting the size of the virtual disk on the host to accomodate for deleted data.
-
@BRRABill said:
@Dashrender said:
am I mising something? Isn't shrinking the same as reclaiming?
I don't think so, but I could be wrong.
Reclaiming is adjusting the size of the virtual disk on the host to accomodate for deleted data.
And shrinking is?
-
@Dashrender said:
And shrinking is?
Actually changing the provisioned size of the virtual disk.
So if you set it up for 50GB, you could expand to 60GB, but not shrink to 40GB.
-
So you're asking if, assuming a thin provisioned disk of 50 GB has 40 GB in use, then you delete 20 GB, leaving you with 40 GB actual file.. is there a way to release that now free 20 GB space, reclaiming the RS space.
good question.
-
@Dashrender said:
So you're asking if, assuming a thin provisioned disk of 50 GB has 40 GB in use, then you delete 20 GB, leaving you with 40 GB actual file.. is there a way to release that now free 20 GB space, reclaiming the RS space.
good question.
Right. You can do it in Hyper-V (I think). There is a COMPACT option.
-
@BRRABill said:
@Dashrender said:
So you're asking if, assuming a thin provisioned disk of 50 GB has 40 GB in use, then you delete 20 GB, leaving you with 40 GB actual file.. is there a way to release that now free 20 GB space, reclaiming the RS space.
good question.
Right. You can do it in Hyper-V (I think). There is a COMPACT option.
yeah I'm not surprised.. you can do the same with SQL and Exchange DBs, though it normally (if not completely) requires taking those systems offline.
when i needed to to this for SQL in the past, I just do a backup and restore.. was faster than a compact
