Adding new Local Storage to XenServer.
-
@Ajin said in Adding new Local Storage to XenServer.:
IT an External drive , which i have added to Xenserver with the following command .
xe sr-create name-label="Local Storege 2 LACIE HDD" shared=false device-config:device=/dev/sdc type=lvm
Does your VM actually run from that LaCie drive, or does it run from internal drives on your server?
-
The VM is running from internal drive in my server.
-
@Ajin Welcome back
-
@DustinB3403 said in Adding new Local Storage to XenServer.:
The Lacie drive is not at all local to the server. It's attached storage and therefore not available to be used as "snapshot" storage. If you wanted to use the Lacie as a place to store your actual backups (snapshots are not backups) you could do that.
But using the snapshot functionality, you need space on the disk that is housing the VM.
It is as local to the server as anything else is. It's a DAS unit and therefore identical to the server as if it were inside the chassis.
-
@DustinB3403 said in Adding new Local Storage to XenServer.:
@Ajin said in Adding new Local Storage to XenServer.:
Thanks for the reply Dustin.
My actual need is to take a snapshot of the Development server before making any vital changes in the server , so that i can revert safely if any thing goes wrong , as reverting snapshot will take very little time and easy to perform.
A snapshot can only work if it's on the same drive in which the VM resides. This LACIE drive is external, the only choice you have with this is to create a full backup to this drive and hope for the best. (that whatever changes you have works and that you don't need to revert)
This is the important part. Not that the Lacie is internal or not, but that it needs to be the same block device as the server for snapshots to be able to snap initially.
-
@scottalanmiller said in Adding new Local Storage to XenServer.:
@DustinB3403 said in Adding new Local Storage to XenServer.:
The Lacie drive is not at all local to the server. It's attached storage and therefore not available to be used as "snapshot" storage. If you wanted to use the Lacie as a place to store your actual backups (snapshots are not backups) you could do that.
But using the snapshot functionality, you need space on the disk that is housing the VM.
It is as local to the server as anything else is. It's a DAS unit and therefore identical to the server as if it were inside the chassis.
I'll disagree to this with regards that it's not the same block device. Therefor it's "external" as far as the system cares to use it for this case.
-
@DustinB3403 said in Adding new Local Storage to XenServer.:
@scottalanmiller said in Adding new Local Storage to XenServer.:
@DustinB3403 said in Adding new Local Storage to XenServer.:
The Lacie drive is not at all local to the server. It's attached storage and therefore not available to be used as "snapshot" storage. If you wanted to use the Lacie as a place to store your actual backups (snapshots are not backups) you could do that.
But using the snapshot functionality, you need space on the disk that is housing the VM.
It is as local to the server as anything else is. It's a DAS unit and therefore identical to the server as if it were inside the chassis.
I'll disagree to this with regards that it's not the same block device. Therefor it's "external" as far as the system cares to use it for this case.
That cannot be correct simply because you can have thousands of totally different block devices all equally local and internal to the chassis. One is not more internal or local than the other. I have two totally independent block devices on the latest VM that I built. They are totally unrelated to each other, but both are equally local.
Two different block devices can even come from the same physical drive!
-
@scottalanmiller said in Adding new Local Storage to XenServer.:
@DustinB3403 said in Adding new Local Storage to XenServer.:
@scottalanmiller said in Adding new Local Storage to XenServer.:
@DustinB3403 said in Adding new Local Storage to XenServer.:
The Lacie drive is not at all local to the server. It's attached storage and therefore not available to be used as "snapshot" storage. If you wanted to use the Lacie as a place to store your actual backups (snapshots are not backups) you could do that.
But using the snapshot functionality, you need space on the disk that is housing the VM.
It is as local to the server as anything else is. It's a DAS unit and therefore identical to the server as if it were inside the chassis.
I'll disagree to this with regards that it's not the same block device. Therefor it's "external" as far as the system cares to use it for this case.
That cannot be correct simply because you can have thousands of totally different block devices all equally local and internal to the chassis. One is not more internal or local than the other. I have two totally independent block devices on the latest VM that I built. They are totally unrelated to each other, but both are equally local.
Two different block devices can even come from the same physical drive!
My point is, for the use of Snapshot it's a different block device, external to the one in which the VM lives. It can't be used to create snapshots.
-
@scottalanmiller Thankyou .
I was just testing moving the VM to the new storage , moved the VM to the new storage , changed the mac id and it works good , Now i can take snap since the vm resides in the new storage with enough space for snapshot
-
@Ajin said in Adding new Local Storage to XenServer.:
@scottalanmiller Thankyou .
I was just testing moving the VM to the new storage , moved the VM to the new storage , changed the mac id and it works good , Now i can take snap since the vm resides in the new storage with enough space for snapshot
Great!
-
Thank-you all for the valuble suggetions
-
@Ajin said
I was just testing moving the VM to the new storage , moved the VM to the new storage , changed the mac id and it works good , Now i can take snap since the vm resides in the new storage with enough space for snapshot
It's awesome when it works like that, right?
-
Yes It is
-
Another ML success story
