This message was deleted.
# citrix-vad
s
This message was deleted.
l
I don't think so mate no. Once you've gone through that process the linked template is already copied into each storage location.
j
Super, thanks
👍🏻 1
j
Only thing I can think of is possibly rollback issue depending on hypervisor…
j
Hmmm yes, that would obviously not be possible without the previous image. Maybe will add a note to do it only after new image has been up for a few days
l
That should still be okay too as the snapshot that's copied to each storage location will still be there too.
j
Ah right
l
But I hear what Jarian is saying and I've never "pressed the buttons in this order" so no guarantee. In theory though, promoting a new image copies a new base clone to each storage location and retains the previous one for rollback. It doesn't rely on the original VM.
j
it all sounds good enough for my current predicament, so happy days
l
Just say "Leee said" if it all goes wrong.
😀 2
j
I don’t think that’s equal on all hypervisors and how they handle image management.
👀 1
k
Yeah, if you're on ESX the snapshot is a flattened copy of the golden image. You'll be fine in a running state but as Jarian said, rollback can become problematic.
I wouldn't take the risk if this is a 'to-be' procedure and keep that image around for X period of time.
⤴️ 1
👍🏻 1
j
Part of the image update process here involves manually cloning the golden image to a second datacenter and I don't want them to get in the habit of leaving stacks of copies of it lying about. But giving it a week or so to bed in should be reasonable enough. Very small customer I am trying to hand over to with zero Citrix skills, so you can imagine the shenanigans
m
If this is Azure, James has a kickass automation script to handle replication between datacenters and cleanup
j
Sadly not