Тёмный

Citrix XenApp Datastore Migration- Step by Step - Part 2 

Pro Hut
Подписаться 2 тыс.
Просмотров 6 тыс.
50% 1

Citrix XenApp Datastore Migration- Step by Step - Part 2
www.prohut.net: In this video we followed step by step approach of migrating Citrix Datastore (Database) from SQL Express to SQL Server.
Channels to contact ProHut IT Services:
Facebook : / prohutitservices
Linedin: / prohut
Twitter: / prohutindia
Google Plus: plus.google.co...
RU-vid: / prohutindirapuram
Blog: www.prohut.net/...
Skype ID: ProhutIndia
Transcript:
Hello Friends, Welcome back to ProHut IT Services. Good to see you back.
In the last video, we learned the steps of creating DSN file.
In this video we'll learn the steps of migrating Datastore from SQL Express to SQL Server.
Very first step is to copy data from existing database to newly created bland database.
We need to use the command dsmaint migrate to migrate Citrix Datastore.
Let's review the complete command that we need to run.
SRCDSN means source DSN file.
In our demo source dsn is MF20.dsn file. It created automatically when we configured Citrix XenApp Server.
We need to give full path of source dsn file. And don't forget to use double quotes as we have space in the entire path.
SRCUser is the user who has admin access on the source datastore. In the last video we have seen that user id TU1 has admin access on both source and destination Databases, therefore we'll select TU1 user id.
Please ensure that you use prefix domain name, as TU1 is a domain user and not local user.
SRCPWD is source password i.e. password of TU1. If you don't want to type the password of user on the screen then you can even type "*", instead of typing the password of user.
In this demo, we are already logged in with TU1 user id therefore it might not ask for the password.
DSTDSN is destination DSN file i.e. CTXDSN.dsn file. This is the same file that we created in last video.
Destination DSN file contains information about the destination database to which we want to migrate the data.
DSTUser is the Destination user. In this demo we are using same user id i.e. TU1 as source and destination user id.
DSTPwd is the destination password. If you don't want to display password then you can type "*" instead of typing full password.
Next step is to copy the entire command and paste the same in command prompt and hit enter to run the command.
We got a pop-up to verify if the new database is on the supported list of Citrix or not.
This is very valid point. As Citrix supports either SQL or Oracle as datastore.
In this demo, we are using SQL Server.
Click on Yes to continue.
Migration is in process.
Migration is completed successfully.
Next step is to compare the source datastore with destination datastore.
It is good practice to compare both source and destination datastore.
Click on Yes to compare them.
Comparison completed successfully.
And the destination datastore matches source datastore.
This confirms the migration of datastore from SQL Express to SQL Server.
Citrix XenApp is still using old DSN file i.e. MF20.dsn.
We need to configure Ctirx to use new DSN file i.e. CTXDSN.dsn file.
Let's review the command that we need to use to configure Citrix XenApp to use new DSN file.
Command is DSMaint Config command.
As we want Citrix XenApp to use new DSN file therefore we need to provide information of destination user, destination password and destination DSN file.
This is the completed command that we need to run.
User id is TU1.
Password that we have configured is pass@123
DSN is the destination dsn file i.e. CTXDSN.dsn.
Please ensure that you specify complete path of dsn file and it should be within double quotes.
Let's copy the command and run the same in command prompt.
Configuration changed successfully.
It is suggesting to restart IMA service.
Let's restart IMA service to complete the process.
IMA service will not start , if the process is not successful
IMA service started successfully that confirms that migration and configuration process is completed successfully.
Let's open registry to verify, if Citrix XenApp is using new DSN file or still using old MF20.dsn file.
Browse the path that is highlighted on the screen.
As we can see that Citrix is using new DSN file now i.e. CTXDSN file
Next step is to open Citrix Appcenter to check if it's working or not.
It looks good, we can see our Citrix farm and an application that we published.
Hope you enjoyed this video.
If you liked this video then please don't forget to click on thumbs up, subscribe and share this video.
Bye Friends, keep smiling and have fun.

Опубликовано:

 

16 сен 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 10   
@hectorrios1750
@hectorrios1750 8 лет назад
Excellent, thanks.
@prohut
@prohut 7 лет назад
Hi Hector, Please visit www.itingredients.com, it has many more detailed articles for your reference. Don't forget to share your feedback about the same.
@betaproonline
@betaproonline 7 лет назад
Nice video, very helpful. Thanks
@prohut
@prohut 7 лет назад
Hi, Please visit www.itingredients.com, it has many more detailed articles for your reference. Don't forget to share your feedback about the same.
@sanjaymalik574
@sanjaymalik574 8 лет назад
so if i have 10 XenApp server in my env. then do i need to run this command on all of those servers?
@prohut
@prohut 8 лет назад
+Sanjay Malik Which command you are referring to, please elaborate the question.
@sanjaymalik574
@sanjaymalik574 8 лет назад
+Pro Hut I am referring to DSMAINT Config command which you have used to configure CTX01 server to use new DSN File (CTXDSN). I want to know if i need to run this command on all 10 servers in my environment if i decide to migrate the database?
@prohut
@prohut 8 лет назад
+Sanjay Malik Yes you need to run DSMAINT config command on all the Citrix XenApp servers with the new DSN file else you can use any script to run the command on all the servers.
@abdulmuminbashir2550
@abdulmuminbashir2550 9 лет назад
The background music is annoying.
@prohut
@prohut 9 лет назад
Abdulmumin Bashir Will try to change to different music.
Далее
Microservices with Databases can be challenging...
20:52
Добрая весть 😂
00:21
Просмотров 307 тыс.
An Illustrated Guide to OAuth and OpenID Connect
16:36
Просмотров 588 тыс.
Postgres Internal Architecture Explained
33:16
Просмотров 151 тыс.