Not of which I am aware, you would have to run the install on one of your VMHosts and then use that as a template etc. Shout if I missed something here, but I think this is what you wanted to know, we do not have any VM templates that we provide...
Cheers, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
Hey Tim, what are you doing as far as your Root Folder and Folder Mounts in QVS? Those will need to be UNC paths with the cluster, and that poses a bit of a chicken and egg situation! 🙂 What I would probably do in this case is if you have your new folders all ready to go and the apps all copied over etc., switch the existing server to those folders, that will update the Settings.ini file etc. So if that works, then you can go ahead and do your install on your two new nodes and start things to be sure things look good, but be sure you stop the old QVS service at this point and use the existing QVS resource you already have configured in the QMC to point to the new servers by changing the existing QVP address on the General tab settings to one of the new nodes, and once that node is up, then you can add the other node. Oh, I forgot to ask if we modified your existing QVS license, or did we give you a new one, if we modified existing, check the license in QMC to be sure you see ClusterNodes and a 2 in the LEF. If that is good, then I think you are good with the above. Sorry this does not flow very well, have a read and shout back if anything is too confusing and I can try to clarify for you, but hopefully this makes sense.
Regards, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
Hey Tim, ok, so the LEF you dropped shows you just have a single node on that license, that is not going to work for your new environment. If you did get a new license for that environment, then that would be good, as that means you can leave the old one running while you get the new environment up and running etc... You are looking for a 2 in the Number of Cluster Nodes line, that is what will allow you to properly configure things, so be sure you have that on the license you are going to use in the new environment, otherwise I would let Orders or your account manager know things are not right.
Since you do have a Test license, that should mimic prod as well, so if you have two nodes allowed in prod, I believe you should get nodes in Test as well, but I am not certain on that one, need to check with your account manager for sure there. I know the CALs should be a replica though, whatever you have in Prod, you should have exactly the same on your Test key...
The real trick is to not run the same license in more than one environment, that is how you avoid any issues, so as long as you keep that in mind, I think everything will be good, oh, well, one other thing would be to not have two different environments using the same file shares. I think the safe bet is to leave existing environment pointed where it is and have new environment use new shares, and you get the new all pointed to the right places etc., and then you should be good to go.
Where is your QMS and QDS/Publisher or Reload Engine running, is that moving as well, or are you just adding the two new QVS nodes and everything else stays where it is? If the latter, then things are pretty easy, when you shut down the old QVS and bring the new ones online, just modify the existing QVS resource in the QMC by changing the QVP service URL to point to one of the new servers and then add the second node via the green + button etc. Hopefully this is all making sense, but I think from what you have been saying you have a decent plan in place, shout if you have further questions.
Regards, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
Hey Tim, I am a little confused! 🙂 What will Server 3 be running? I just want to be sure I am on the right page here. Given you are moving things from Server 1 to Server 2, you are likely going to want to migrate your QVPR, that way you will not have to setup your tasks and stuff again, but note, you want to leave the QDS folders with the same structure as you have on Server 1 currently, otherwise you will need to change those paths in the QVPR files directly versus using the QMC, as doing it in the QMC will cause new GUIDs to generate and break all your task links! 🙂 Just wanted to point that out, so you do not get burned on that one.
Before I say anything more, I want to know what is going to run on Server 3, so I do not confuse you further! 🙂
Server 2 is going to run QMS, QVS, QDS, DSC and QVWS?
Server 3 is going to run only QVS?
Do you have a Publisher license, or just Reload Engine?
Cheers, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
yes i could migrate it from server 1 to server 2. But i cannot migrate on a weekend and have to do it between Monday and friday. Thats why i need to let both running simultaneously while i do the migration.
Yes i have Publisher Licence.
Server 3 is the node from Server 2. Yes i think its only QVS but please correct me if i'm false. QMC should be only available on Server 2. QDS also cause i dont have this service clustered. QVWS will be outsourced in a VM
My main question is still "Can i change the CAL from server to my test licence?". Regards
Tim, provided your Test license has the same CALs as Prod, you could use that in the new environment to check things out etc. prior to swapping out the actual production license, but the users will see the Test watermark on all the objects etc., just FYI. As long as they will not mind that, then I would say that is likely your best option here, as again, you do NOT want to run the same license key on two environments, as that is most likely going to cause one of them to go down for sure...
What I would really recommend here is you consider getting up with your account/services manager to see about potentially engaging with them to have them do a use case review etc. to be sure you are on the right track with everything, that way you will be sure the direction you are going is the best path forward for you guys.
Regards, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
Thank you. Thats exactly what i already did. I told them what i want to do and it will work as intended.
i got a migration licence for that case. (didnt know that there is such a licence) With that licence i have 30 days time to migrate and there is no risk that new and old environment will cluster cause now i have 2 different CAL's and 2 different Root Folders.
.png "Former Employee"){kind=icon}
