<?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: SAS Backup failed in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/432825#M12105</link>
    <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your assistance.&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jan 2018 16:34:07 GMT</pubDate>
    <dc:creator>LJalaja</dc:creator>
    <dc:date>2018-01-31T16:34:07Z</dc:date>
    <item>
      <title>SAS Backup failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/431689#M12081</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We are running SAS 9.4 on Linux.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am attempting to backup our SAS environment, but SAS Backup Manager is not working.&lt;/P&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;When I try to run an ad-hoc backup, I got the following error:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;result&lt;BR /&gt;type: backup&lt;BR /&gt;status: not started&lt;BR /&gt;size: 0&lt;BR /&gt;&lt;BR /&gt;errorEntries&lt;/DIV&gt;&lt;DIV class="sapMBarContainer sapMBarRight"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV class="sapMDialogScroll sasMDialogScroll"&gt;&lt;DIV class="sapMDialogScrollCont sasMDialogScrollCont"&gt;An error occurred while fetching history information.&lt;/DIV&gt;&lt;DIV class="sapMDialogScrollCont sasMDialogScrollCont"&gt;statusCode: 603&lt;BR /&gt;name: ERROR_CODE_GET_HISTORY_ERROR&lt;BR /&gt;category: History&lt;/DIV&gt;&lt;DIV class="sapMDialogScrollCont sasMDialogScrollCont"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="sapMDialogScrollCont sasMDialogScrollCont"&gt;And the scheduled meta server backup in SASMC failed but the adhoc backup was working fine.&lt;/DIV&gt;&lt;DIV class="sapMDialogScrollCont sasMDialogScrollCont"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="sapMDialogScrollCont sasMDialogScrollCont"&gt;&lt;DIV&gt;Please let me know if you have any ideas or suggestions.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thank you,&lt;/DIV&gt;&lt;DIV&gt;Jalaja&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 29 Jan 2018 07:10:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/431689#M12081</guid>
      <dc:creator>LJalaja</dc:creator>
      <dc:date>2018-01-29T07:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Backup failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/432554#M12095</link>
      <description>&lt;P&gt;It is possible that your backup history file is corrupt.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Try renaming the &lt;FONT face="courier new,courier"&gt;BackupHistory.xml&lt;/FONT&gt; file to &lt;FONT face="courier new,courier"&gt;BackupHistory_old.xml&lt;/FONT&gt; in the following locations:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The central vault location (can be located on the Policy page of the Backup Manager)&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;&lt;STRONG&gt;&lt;EM&gt;configuration-directory&lt;/EM&gt;\Lev&lt;EM&gt;n&lt;/EM&gt;\Backup\dropzone&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;&lt;STRONG&gt;&lt;EM&gt;configuration-directory&lt;/EM&gt;\Levn\Web\WebAppServer\SASServer1_XX\temp\SASDeploymentBackup_APPHOME&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This will force the BackupHistory.xml files to be regenerated on the next backup.&amp;nbsp;Re-run the backup and see if it completes successfully.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 22:46:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/432554#M12095</guid>
      <dc:creator>AndyForeman</dc:creator>
      <dc:date>2018-01-30T22:46:02Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Backup failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/432567#M12096</link>
      <description>&lt;P&gt;Hi Jalaja,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Deployment Backup and Recovery Tool saves information about each backup and recovery in a BackupHistory.xml&lt;BR /&gt;file.&amp;nbsp; Based on the error reported by the tool it is possible that the one or more copies of this file&lt;BR /&gt;is damaged and the tool is unable to parse the file.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can check to see if this is the reason for the problem by looking at the &amp;lt;sasconfigdir&amp;gt;/Lev1/Web/Logs/SASServer1_1/SASDeploymentBackup9.4.log file and searching the file for:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Error Code: 603&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Caused by: org.xml.sax.SAXParseException&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can try renaming each copy of the file and then run your ad-hoc backup which will create a new BackupHistory.xml file although you will lose previous history information.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Look for a copy of the BackupHistory.xml file on each tier in these locations and rename the file to something like old.BackupHistory.xml and then run the backup again.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&amp;lt;sasconfigdir&amp;gt;/Lev1/Backup/Vault&lt;BR /&gt;&amp;lt;sasconfigdir&amp;gt;/Lev1/Backup/dropzone/conf&amp;nbsp; (or &amp;lt;sasconfigdir&amp;gt;/Lev1/Backup/dropzone for pre 9.4M3 )&lt;/P&gt;
&lt;P&gt;On the middle tier:&lt;/P&gt;
&lt;P&gt;&amp;lt;sasconfigdir&amp;gt;/Lev1/Web/WebAppServer/SASServer1_1/temp/SASDeploymentBackup_APPHOME&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If your middle tier is clustered you would need to rename the file for each SASServer1_N instance.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If this doesn't resolve the problem then I recommend opening a track with SAS Technical Support.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Michele&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 23:38:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/432567#M12096</guid>
      <dc:creator>michele_sas</dc:creator>
      <dc:date>2018-01-30T23:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Backup failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/432825#M12105</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your assistance.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2018 16:34:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Backup-failed/m-p/432825#M12105</guid>
      <dc:creator>LJalaja</dc:creator>
      <dc:date>2018-01-31T16:34:07Z</dc:date>
    </item>
  </channel>
</rss>

