Hello ilya, If I am not mistaken, while adding secondary storage NFS server ip and path is all one specifies in cloud-stack. Running df -h on ACS management server shows you secondary storage mounted there. Don't think hypervisor sees NFS (even if primary storage and NFS coming from same storage box). Plus, while doing activities like VM deploy and snapshot things always move from secondary to primary via SSVM.
Have you actually seen any setup where you have verified this? @ cs user, When you're moving the volumes, are those attached to running VM? or those are just standalone orphan volumes? -- Makrand On Thu, Aug 25, 2016 at 4:24 AM, ilya <[email protected]> wrote: > Not certain how Xen Storage Migration is implemented in 4.5.2 > > I'd suspect legacy mode would be > > 1) copy disks from primary store to secondary NFS > 2) copy disks from secondary NFS to new primary store > > it might be slow... but if you have enough space - it should work... > > My understanding is that NFS is mounted directly on hypervisors. I'd ask > someone else to confirm though... > > On 8/24/16 7:20 AM, cs user wrote: > > Hi All, > > > > Xenserver 6.5, cloudstack 4.5.2. NFS primary storage volumes > > > > Lets say I have 1 pod, with 2 clusters, each cluster has its own primary > > storage. > > > > If I migrate a volume from one primary storage to the other one, using > > cloudstack, what aspect of the environment is responsible for this copy? > > > > I'm trying to identify bottlenecks but I can't see what is responsible > for > > this copying. Is it is the xen hosts themselves or the secondary storage > vm? > > > > Thanks! > > >
