<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Best practice for full backup in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Best-practice-for-full-backup/m-p/20847#M4351</link>
    <description>We don't stop the services, we just do the backup.  The odds of our finding a time with no SAS job running is virtually 0, so we decided the cost of not getting every data set every time was less than the cost of unhappy users.&lt;BR /&gt;
&lt;BR /&gt;
We run daily incremental backups and weekly full backups (of everything on the server), so we generally get data sets backed up as soon as the user is done with it.&lt;BR /&gt;
&lt;BR /&gt;
Our environment sounds bigger than yours, but we've been doing it this way since we had just 20 users or so.  Users seem to find it a reasonable balance between safety and convenience.  The downside for you as a sysadmin is that you may have to look multiple places to find the file to restore.&lt;BR /&gt;
&lt;BR /&gt;
Doc Muhlbaier&lt;BR /&gt;
Duke</description>
    <pubDate>Mon, 20 Apr 2009 12:54:57 GMT</pubDate>
    <dc:creator>Doc_Duke</dc:creator>
    <dc:date>2009-04-20T12:54:57Z</dc:date>
    <item>
      <title>Best practice for full backup</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Best-practice-for-full-backup/m-p/20846#M4350</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
I lightly manage a SAS 9.1.3 SP4 Server on Windows Server 2003. I had to backup it and I want to do it by scripts.&lt;BR /&gt;
&lt;BR /&gt;
As I want to perform a full backup of the non-system partition containing SAS folders, I plan to :&lt;BR /&gt;
  - stop SAS/other services (to avoid modifications or even connections),&lt;BR /&gt;
  - backup the partition,&lt;BR /&gt;
  - start needed services.&lt;BR /&gt;
&lt;BR /&gt;
Unfortunately, I don't know exactly which services have to be stop... I think "SAS Lev1 MS - EGServers" and "SAS Lev1 OB - EGServers" are both of them because there are the only SAS services. But is there others ?&lt;BR /&gt;
&lt;BR /&gt;
Thanks for your answers.</description>
      <pubDate>Mon, 20 Apr 2009 10:06:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Best-practice-for-full-backup/m-p/20846#M4350</guid>
      <dc:creator>HalfTimeSasAdmin</dc:creator>
      <dc:date>2009-04-20T10:06:36Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for full backup</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Best-practice-for-full-backup/m-p/20847#M4351</link>
      <description>We don't stop the services, we just do the backup.  The odds of our finding a time with no SAS job running is virtually 0, so we decided the cost of not getting every data set every time was less than the cost of unhappy users.&lt;BR /&gt;
&lt;BR /&gt;
We run daily incremental backups and weekly full backups (of everything on the server), so we generally get data sets backed up as soon as the user is done with it.&lt;BR /&gt;
&lt;BR /&gt;
Our environment sounds bigger than yours, but we've been doing it this way since we had just 20 users or so.  Users seem to find it a reasonable balance between safety and convenience.  The downside for you as a sysadmin is that you may have to look multiple places to find the file to restore.&lt;BR /&gt;
&lt;BR /&gt;
Doc Muhlbaier&lt;BR /&gt;
Duke</description>
      <pubDate>Mon, 20 Apr 2009 12:54:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Best-practice-for-full-backup/m-p/20847#M4351</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2009-04-20T12:54:57Z</dc:date>
    </item>
  </channel>
</rss>

