BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.

Hi All,

 

Can any one suggest steps for multi tier migration with common metadata 

through SAS Migration Utility.

 

Regards,

Kaushal Solanki

1 ACCEPTED SOLUTION

Accepted Solutions
Mark_sas
SAS Employee

What David and the doc are saying is that you need to run the SAS Migration Utility on each on each distinct tier (metadata, compute, and middle tier), and each time you do, you point to the same output migration package directory.  Storing the migration package directory in shared filespace makes this easier, but if you can't do that, you'll need to copy/ftp the package from one tier to the next after you've run the SAS Migration Utility on each.  In this way, it accumulates the migration content for all tiers in the same package directory.  You then take this consolidated package to your target tiers, running the SAS Deployment Wizard on each, and pointing to the same migration package for each (starting with the metadata server and following the tier order as described in the doc).


Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF

View now: on-demand content for SAS users

View solution in original post

5 REPLIES 5
Mark_sas
SAS Employee

There's a lot of useful documentation on the topic of migration, rooted at http://support.sas.com/rnd/migration/.  Multi-tier environments are covered in detail in the linked documentation, especially the SAS 9.4 Migration Guide.  Those are great places to start.

 

 


Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF

View now: on-demand content for SAS users

kaushalsolanki
Quartz | Level 8

Hello Mark,

 

Thank you for your reply, Have completed Metadata Miration successfully.

 

But when i am trying it for another tier, In properties file have mention 

SMU.host.metadata=(Metadata server ip), it is giving me an error as below.

 

SMU Not metadata tier because server address :Metadata Server IP != this host IP

 

Regards,

Kaushal Solanki

 

dpage
SAS Employee

On your second machine, are you pointing to a shared output location, the smu package output copied from the metadata server SMU run or a blank output directory? You'll see an error like this when the SMU detects no metadata server present in the SMU output location, and the current machine isn't the metadata server. 

 

From the Appendix 1 of the guide Mark linked:

 

"On SAS multiple-machine deployments, the migration utility must be able to write to (and read from) its output directory.
We recommend that the utility output directory be on shared network storage accessible to every SAS machine in the deployment."

 

And from the smu.properties.template

 

# The migration package output directory. It will be
# created if this is being run against the metadata server
# tier. Otherwise, it should already contain the results
# from your metadata server tier run and any other upstream
# tiers. The results from every tier of your deployment
# should be included in the same migration package.

kaushalsolanki
Quartz | Level 8

Hello dpage,

 

Thank you for your reply so according to you i have to use the same migration package,

for all other tiers Which is generated from Metadata Tier ?

 

As per migration guide i need to run SMU analysis for each tier.

 

Regards,

Kaushal Solanki 

Mark_sas
SAS Employee

What David and the doc are saying is that you need to run the SAS Migration Utility on each on each distinct tier (metadata, compute, and middle tier), and each time you do, you point to the same output migration package directory.  Storing the migration package directory in shared filespace makes this easier, but if you can't do that, you'll need to copy/ftp the package from one tier to the next after you've run the SAS Migration Utility on each.  In this way, it accumulates the migration content for all tiers in the same package directory.  You then take this consolidated package to your target tiers, running the SAS Deployment Wizard on each, and pointing to the same migration package for each (starting with the metadata server and following the tier order as described in the doc).


Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF

View now: on-demand content for SAS users