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

Hello,

 

We are planning to set up a DR Environment for our existing SAS Prod Environments on Unix.

 

We are currently on SAS 9.4 M3.

 

Is it possible to take a backup of the existing /SASHome & /Lev directories. And do a restore on the new DR Servers ?

 

Also, does it require the need to make any changes to the configurations on the DR Servers to match the hostnames & other relevant changes between the Prod & the DR Unix boxes ?

 

Thanks & Regards !

1 ACCEPTED SOLUTION

Accepted Solutions
JuanS_OCS
Amethyst | Level 16

Hi,

 

a very simplified configuration (and efficient) for DR would be to have:

 

- 2 hosts, with just the OS and the pre-requisites

- 1 CFS (clustered file system), where you will have the SAS config, SAS binaries and all the user data.

- have SAS configured based on alias (so you can just change the alias on the DNS to point to the new host, when one "dies").

- mount the CF directories on the active host.

- register the alias/host on the DNS.

 

On this way the server and the file system will have DR.

 

As you have now your Production system already configured, a way to go to minimize the impact might be:

 

- Make a good backup of your Production server

- Start creating the pasive/DR server, with different hostname and align pre-requisites with primary/active production.

- Create the CFS (if not yet ready), and start by making the sync (beware of permissions an lost soft and hard links!)

- Stop the Production/primary server's SAS services and SAS processes.

- Make an extra sync when you can stop the server -->

- change hostname of the primary/current Production server.

- create the DNS alias and make it the same as the current hostname.

- point that alias on the DNS server to the primary server (current production, which now has a different hostname)

- mount the CFS on the primary --> the folder structure and permissions should be the same as on your current status on the Production server.

- Start the SAS services on the primary server, which should now work fine as before.

 

When the primary goes down, stop all SAS services and SAS processes on the primary/production server,  change the DNS alias on the DNS server to point to the secondary, change network cards and un mount the CFS from the primary and mount it on the secondary. Then start the services on the secondary.

View solution in original post

5 REPLIES 5
GyaniBaba
Obsidian | Level 7

what type of setup you want active-active or active passive?

it is not mandatory that both live and dr have same type of architecture. you need to have cerain servers similar to your live and install sas on those, make them working, now you must have network file systems that can be mounted to your DR, in case of failure or if you want to keep different sets of disks, you would need to configure rsync.

 

 

Virtual IP can be configured by your infrastructure team to enable DR.

 

would you provide some more details about your sas architecture before recommended approach can be put?

JuanS_OCS
Amethyst | Level 16

Hi,

 

a very simplified configuration (and efficient) for DR would be to have:

 

- 2 hosts, with just the OS and the pre-requisites

- 1 CFS (clustered file system), where you will have the SAS config, SAS binaries and all the user data.

- have SAS configured based on alias (so you can just change the alias on the DNS to point to the new host, when one "dies").

- mount the CF directories on the active host.

- register the alias/host on the DNS.

 

On this way the server and the file system will have DR.

 

As you have now your Production system already configured, a way to go to minimize the impact might be:

 

- Make a good backup of your Production server

- Start creating the pasive/DR server, with different hostname and align pre-requisites with primary/active production.

- Create the CFS (if not yet ready), and start by making the sync (beware of permissions an lost soft and hard links!)

- Stop the Production/primary server's SAS services and SAS processes.

- Make an extra sync when you can stop the server -->

- change hostname of the primary/current Production server.

- create the DNS alias and make it the same as the current hostname.

- point that alias on the DNS server to the primary server (current production, which now has a different hostname)

- mount the CFS on the primary --> the folder structure and permissions should be the same as on your current status on the Production server.

- Start the SAS services on the primary server, which should now work fine as before.

 

When the primary goes down, stop all SAS services and SAS processes on the primary/production server,  change the DNS alias on the DNS server to point to the secondary, change network cards and un mount the CFS from the primary and mount it on the secondary. Then start the services on the secondary.

GyaniBaba
Obsidian | Level 7

agree, thanks

tiadmin
Fluorite | Level 6

Hi Juan,

 

That was very detailed & helpful explanation.

 

Appreciate the quick response.

 

Regards..

JuanS_OCS
Amethyst | Level 16

Thanks to you for your question, it was a great one (love it). I think it is an important and recursive question. And on Linux/Unix is to easy to arrange...!

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 2006 views
  • 2 likes
  • 3 in conversation