Architecting, installing and maintaining your SAS environment

Steps For Multi-Tier Migration with Common Metadata.

Accepted Solution Solved
Reply
Contributor
Posts: 63
Accepted Solution

Steps For Multi-Tier Migration with Common Metadata.

Hi All,

 

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

through SAS Migration Utility.

 

Regards,

Kaushal Solanki


Accepted Solutions
Solution
‎12-01-2015 02:02 AM
SAS Employee
Posts: 102

Re: Steps For Multi-Tier Migration with Common Metadata.

Posted in reply to kaushalsolanki

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).

View solution in original post


All Replies
SAS Employee
Posts: 102

Re: Steps For Multi-Tier Migration with Common Metadata.

Posted in reply to kaushalsolanki

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.

 

 

Contributor
Posts: 63

Re: Steps For Multi-Tier Migration with Common Metadata.

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

 

SAS Employee
Posts: 102

Re: Steps For Multi-Tier Migration with Common Metadata.

Posted in reply to kaushalsolanki

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.

Contributor
Posts: 63

Re: Steps For Multi-Tier Migration with Common Metadata.

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 

Solution
‎12-01-2015 02:02 AM
SAS Employee
Posts: 102

Re: Steps For Multi-Tier Migration with Common Metadata.

Posted in reply to kaushalsolanki

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).

🔒 This topic is solved and locked.

Need further help from the community? Please ask a new question.

Discussion stats
  • 5 replies
  • 766 views
  • 0 likes
  • 3 in conversation