BookmarkSubscribeRSS Feed
BharathV
Calcite | Level 5

We are setting up DR servers which need to be in sync with Production environment. So we require content server to be in sync along with metadata.

How to synchronize prod content server with DR? What all things need to be considered during synchronization.

 

3 REPLIES 3
SASKiwi
PROC Star

As far as I'm aware SAS doesn't provide scripts for synchronisation of environments, So it is up to you to build your own.

 

What OS do your SAS servers run on? Ours run on Windows Server, so we have Powershell scripts which use Robocopy to do daily metadata and SAS data / applications synchronisation. The SAS Prod server processes need to be closed so up-to-date SAS metadata can be copied, then started up again afterwards. Metadata synchronisation is simply done by copying the OS folders where the SAS metadata is stored. This is a lot easier than exporting and importing content.

 

What tools you use will most likely depend on your OS and its functionality.

BharathV
Calcite | Level 5
We are running in Linux environment. We use import export scripts for metadata synchronisation, but content server is not part of metadata.

If we want to use DR both metadata and content server should have same day copy of production. But we are not sure how to be in sync with prod content server.

As you are also using DR, didn’t you setup both metadata and content server synchronisation with prod?

SASKiwi
PROC Star

Yes, we have, via overnight synchronisation. That means we are no more than one day behind in DR which we regard as acceptable.for our standard of business continuity.

sas-innovate-2024.png

Available on demand!

Missed SAS Innovate Las Vegas? Watch all the action for free! View the keynotes, general sessions and 22 breakouts on demand.

 

Register now!

Mastering the WHERE Clause in PROC SQL

SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 532 views
  • 0 likes
  • 2 in conversation