Backing Up SAS Content In Your SAS 9 Enterprise Intelligence Platform

Transcription

1 WHITE PAPER Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Cnsideratins fr Creating Backups f Yur SAS Cntent

2

3 Table f Cntents Intrductin...1 Understanding the SAS Enterprise Intelligence Platfrm... 1 Establish a Frmal Backup Prcess... 3 Define Specific Lcatins fr Physical Cntent... 3 Schedule Backups... 4 Stre Backups... 5 Backing Up the SAS 9 Envirnment... 6 Backing Up Metadata... 7 Perfrming the Metadata BackUp Prcess... 7 Changing the State f the Metadata Repsitry... 9 Backing Up WebDAV File System Relatinal Database fr Xyths External Strage Backup WFSDump Utility Backing Up Physical Cntent Cnsideratins fr SAS Data Files Cnsideratins fr SAS Scalable Perfrmance Data Server Cnclusin References i

4

5 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Intrductin SAS Enterprise Intelligence sftware creates and delivers enterprise intelligence thrugh an integrated suite f sftware technlgies and slutins, all based n the fundatin f the SAS Intelligence Architecture. Specifically, this architecture integrates industry-leading SAS applicatins in data warehusing, business intelligence, and analytic intelligence in a single, chesive platfrm. These capabilities prvide the end-t-end intelligence infrastructure necessary t ensure cnsistent and reliable enterprise-wide intelligence that is needed fr explring, analyzing, and understanding yur business. SAS recgnizes that yur rganizatin has made a cnsiderable investment in yur SAS sftware system. Infrmatin abut the envirnment, reprts generated by end-users, and analytical mdels that drive strategic decisins represents key crprate assets that directly impact business results. Therefre, yur SAS assets must be included in yur crprate backup strategy. This dcument fcuses n cnsideratins fr develping a cntent backup strategy fr the SAS 9 Enterprise Intelligence Platfrm including cntent frm SAS Data Integratin Server, SAS Enterprise BI Server, and analytic prducts such as SAS Enterprise Miner. SAS typically generates perating system files, s standard backup tls can be used t create backups f mst cntent. Hwever, there are cnsideratins that can make yur backup prcess mre effective. This paper is nt intended t prvide a cmplete backup discussin, as we d nt discuss back ups f cnfiguratin files, specific backup systems, r backup management prcesses fr archiving and strage. Peridically, this paper will be updated t include additinal tpics. This paper is written fr SAS system administratrs wh are respnsible fr maintaining the SAS envirnment and ensuring that service levels are met fr yur internal cnstituents. Yu shuld be familiar with the SAS 9 architecture and understand hw cntent is generated and stred in yur envirnment. Understanding the SAS Enterprise Intelligence Platfrm The fllwing discussin is a high-level verview f the SAS Enterprise Intelligence Platfrm. Fr mre detailed infrmatin, see the SAS Intelligence Platfrm: Overview (SAS 2006). The SAS Enterprise Intelligence Platfrm includes cmpnents in the fllwing categries: Data Integratin and ETL The data integratin and extract, transfrm, and lad (ETL) cmpnents enable yu t cnslidate and manage enterprise data frm a variety f surce systems, applicatins, and technlgies. Cmpnents are prvided t help yu cleanse, migrate, synchrnize, replicate, and prmte yur data. Metadata fr all yur intelligence resurces is stred centrally and cntrlled thrugh a single management interface. 1

6 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Business Intelligence The business intelligence cmpnents enable users with varius needs and skill levels t create, prduce, and share their wn reprts and analyses. Easy-t-use interfaces enable users t btain answers t their business questins, but system administratrs retain cntrl ver the quality and cnsistency f the data. Analytics SAS ffers the richest and widest prtfli f analytic capabilities in the sftware industry. The prtfli includes slutins fr statistical data analysis, data and text mining, frecasting, ecnmetrics, quality imprvement, and peratins research. Yu can use any cmbinatin f these tls with the SAS Enterprise Intelligence Platfrm t add extrardinary precisin and insight t yur reprts and analyses. Intelligence Strage The intelligence strage ptins are ptimized fr analytical prcessing. This enables yu t quickly retrieve and reprt n large vlumes f data. The ptins include simple relatinal databases, a threaded multidimensinal database that supprts nline analytical prcessing (OLAP), and relatinal strage with a threaded multiple input/utput (I/O) subsystem fr intensive use by fcused applicatins. These cmpnents in the SAS 9 Enterprise Intelligence Platfrm leverage a cmmn set f servers t generate data, analyses, and reprts. The term server refers t a prgram r prgrams that wait fr and fulfill requests frm client prgrams fr data r services. Each server is cnnected t cntent stres that need t be factred int the backup strategy fr yur SAS envirnment. Whenever yu back up the SAS Metadata Server, yu must als back up these cntent stres. (See Figure 1) Web App Server SAS Metadata Server SAS Applicatin Servers Surce Cde webdav stre Metadata Repsitries SAS Applicatin Servers Surce Cde Database Servers Database Servers SAS Data Servers SAS OLAP Server Data Files Data Files Data Files Cube Files Figure 1. Cntent Strage in the SAS Enterprise Intelligence Platfrm Web App Server Web-based clients, such as SAS Web Reprt Studi and SAS Infrmatin Delivery Prtal, leverage a webdav stre t huse cntent that is surfaced via their interfaces. The recmmended webdav stre in the SAS platfrm is Xyths. 2

7 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Metadata Server The SAS Metadata Server facilitates the sharing f cntent acrss SAS applicatins t prvide a cnsistent representatin f the business t all cnstituents in yur rganizatin. All SAS applicatins leverage the SAS Metadata Server t stre infrmatin abut their cntent in the metadata repsitries. Applicatin Servers - The SAS applicatin servers execute SAS analytical and reprting prcesses fr distributed clients. The surce cde fr these prcesses is stred in a physical lcatin that is accessible t the server. Types f SAS applicatin servers include the SAS Wrkspace Server and the SAS Stred Prcess Server. Data Servers - Enterprise data includes SAS data (such as data sets, OLAP cubes, r SAS Scalable Perfrmance Data (SPD) Server tables), relatinal database management systems, r Enterprise Resurce Planning (ERP) system tables. These represent the actual physical data stres that feed the SAS platfrm. Establish a Frmal Backup Prcess A frmal backup prcess shuld be established and managed specifically as a key IT prcess. Management versight shuld be prvided t ensure that resurces are available t supprt the backup prcess and t be respnsible fr crrective measures if a backup fails. There shuld be clear dcumentatin regarding the steps required fr cmpleting and archiving backups. The fllwing infrmatin shuld be included in the dcumentatin: Stpping and starting sftware server prcesses Netwrk lcatins f cntent t be backed up Lcatins, media, and restre facilities where backup cpies will be archived Utilities and ther sftware tls required t perfrm the backups Schedule f when backups shuld ccur and related service levels apprpriate fr archive, restre, and scale requirements Ameliratin and recvery prcesses fr situatins where backups fail r take lnger than service levels allw Define Specific Lcatins fr Physical Cntent In the SAS 9 envirnment, applicatins cnsume and create data and cntent that are stred physically in a database, a physical file, r a webdav directry. Physical cntent must be backed up in cnjunctin with the SAS Metadata Repsitries because they are dependent n ne anther and need t stay in synch. 3

8 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm As a best practice, we recmmend that yu specify standard lcatins fr physical cntent in rder t have well-defined lcatins fr creating backups. These lcatins need t be accessible by the user ID that is running the backup prcess. Physical cntent includes: Surce cde directries stred prcesses, analytical mdels, SAS Data Integratin Studi jbs SAS data files and relatinal database systems webdav cntent reprts, dcuments the wrk area fr Platfrm Cmputing Prcess Manager sftware fr scheduled jb flws SAS surce cde directries and data files are standard perating files that can be backed up and recvered using existing backup tls. Relatinal database management systems shuld fllw the recmmended vendr backup strategies, emplying vendr-recmmended sftware and systems. Schedule Backups Backups f the envirnment shuld be a scheduled event. Because the metadata server and relatinal database servers must be paused t back up the repsitries, yu need t have a preset time when this happens, s that users will knw when t expect a shrt perid f dwn time. Hw ften yu need t back up yur envirnment depends n a number f factrs. Activity yu shuld back up mre ften fr a high update envirnment versus an envirnment that is mre static r read-nly. Imprtance t the peratin f yur rganizatin yu shuld back up mre ften if it is critical t the peratins f yur rganizatin t keep the SAS envirnment running. Service Levels because yu have t pause sftware services t cmplete the backup, there will be sme SAS system dwntime assciated with the backup prcess. Yu shuld determine the allwable dwntime t cmplete the backup prcess, and what schedule windw it must reside in. Time needed t recver frm a failure if yu need t recver quickly frm a failure, it is best t make mre frequent full backups. If yu can take mre time r d nt have the netwrk resurces fr multiple full backups, then yu might want t supplement a less frequent full backup with incremental backups. The mre frequent the backups, the mre difficult it might be t schedule them because backing up des interrupt service. Hwever, yu can use snapsht tls in cnjunctin with yur backup prcess t keep dwn time t a minimum. This technique will require apprpriate systems resurces t utilize effectively. 4

9 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm In additin t yur regular, full backup schedule, yu shuld perfrm a full interim backup after any f the fllwing ccurs: Yu change the structure f yur metadata, such as adding a repsitry, deleting a repsitry, r changing the dependencies between tw repsitries. Because there is cntent integratin between repsitries, it is critical that yu keep the structures in synch with a full backup. Yu make significant changes t the metadata cntents, such as bulk lading users and grups frm an external, enterprise data surce, cnducting a full repsitry prmtin, r implementing significant BI applicatin-driven updates. Yu change the structure f yur SAS data files because f changes in yur data integratin prcesses. Fr metadata and its assciated cntent, we recmmend that full backups always be perfrmed. This wuld include backing up all metadata repsitries, webdav stres, and surce cde files assciated t stred prcesses, SAS Data Integratin Studi jbs, SAS Enterprise Guide prjects, and SAS Enterprise Miner mdels. Fr example: Scenari 1: Initial develpment in a new SAS envirnment Back up all cntent daily Scenari 2: Prductin envirnment with limited ad-hc changes Back up metadata and metadata-related cntent weekly Back up SAS data files weekly Back up all cntent bi-weekly Scenari 3: Prductin envirnment with active ad-hc changes Back up metadata and metadata-related cntent daily Back up SAS data files daily Back up all cntent weekly Stre Backups Backups shuld be archived by date and time, s that yu can restre t the state clse t when the failure ccurred. Yu shuld be able t leverage existing backup strage systems fr archiving SAS backups. A cmplete backup f SAS cntent including data surces culd be very large, s yu will need t ensure that yur system has enugh memry and CPU resurces t facilitate the backup. 5

10 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Once the backup has been created, relevant infrmatin shuld be captured, such as the wner ID, the date, and a descriptin f the cntents. In additin, there shuld be dcumentatin abut hw the backup was generated. The dcumentatin shuld include the fllwing infrmatin: The name f the metadata server and its repsitries The physical cntent that is cntained, including file path lcatins The scripts and prcesses that were used t make the backups The lcatin f the actual backup files Backing Up the SAS 9 Envirnment The SAS 9 envirnment creates bth metadata and physical cntent that must remain in synch. As a result, it is critical t incrprate the three key cmpnents int the cntent backup strategy: metadata, webdav cntent, and physical files (such as surce cde files and data files). The natural inclinatin is t back up each cmpnent separately, but because f the integrated nature f the SAS envirnment, yu must back up all cmpnents within the same backup windw. Fr SAS metadata and metadata-related cntent, yu shuld always perfrm a full backup versus an incremental backup. This will ensure that all dependencies and crss-references stay in synch. Incremental backups can be effectively leveraged fr databases, such as relatinal databases r SAS Scalable Perfrmance Data Server tables. T back up the cntent in the SAS 9 envirnment, fllw these general steps: 1. Stp r pause the SAS Metadata Server. 2. Lck dwn write access t physical cntent lcatins, such as surce cde directries and database tables. 3. Back up metadata repsitries. 4. Resume the SAS Metadata Server with its repsitries in read-nly state, s that applicatins can read infrmatin but nt create r edit it. 5. Back up webdav lcatins and physical cntent, such as surce cde files and SAS data files. 6. Resume the SAS Metadata Server t active status when all backups are cmpleted. 7. Restre access t physical cntent lcatins. 6

11 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Backing Up Metadata At the cre f the SAS 9 Enterprise Intelligence Platfrm is the SAS Metadata Server. All applicatins depend n the metadata server t create and access shared resurces and cntent. Therefre, yu shuld plan yur backup strategy arund what is needed fr the metadata server. As a best practice, yu shuld always back up the entire metadata server. Full backups include the Fundatin SAS repsitry and all custm and prject repsitries that are registered n the metadata server. By perfrming full backups, yu ensure that dependencies and crss-references between repsitries are crrectly maintained and that the SAS Metadata Server can be restred t a cnsistent state. Perfrming the Metadata BackUp Prcess The metadata repsitries that underlie the SAS Metadata Server are built n a set f SAS data sets. When the SAS Metadata Server is active, these data sets are in a lcked state; they are essentially inaccessible fr cpying. In rder t back up thse SAS data sets, yu must unlck access t them by pausing the SAS Metadata Server prcess. If the server is nt stpped r paused, the resulting backup might be unusable. If n backup exists r the backup was nt perfrmed crrectly, cmpletely rebuilding the metadata repsitry might be required. Fr detailed backup instructins, see Backing Up and Restring the SAS Metadata Server in the SAS Intelligence Platfrm: Administratin Guide (SAS 2006) 1. Althugh yu can manually back up the SAS Metadata Server, we recmmend autmating the prcess by using the %OMABAKUP macr. The %OMABAKUP macr is a SAS batch interface that enables yu t perfrm a cmplete backup f the SAS Metadata Server. The macr is part f the SAS autcall libraries and runs in a dedicated SAS sessin. In its default mde, %OMABAKUP perfrms the fllwing actins: Pauses the repsitry manager, which changes the access state t read-nly status s that repsitries cannt be added r deleted Pauses each metadata repsitry. The pause peratin des the fllwing: retains all active client cnnectins temprarily changes the repsitry s access state t ffline status s that it stps receiving client requests t read r write metadata. If a client applicatin submits a new request, the client displays a message that tells the user that the server is paused and that the user shuld try the request later. 1 In Nvember 2006, the guide will be called SAS Intelligence Platfrm: System Administratin Guide. 7

12 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm flushes updated metadata frm the server s memry and writes the updated metadata t the metadata repsitry clses the SAS data sets that serve as repsitry cntainers Uses PROC COPY t cpy the metadata server s repsitry manager and all its registered metadata repsitries t a netwrk path that yu specify. Creates cntrl files that cntain infrmatin abut the backup. The user ID that executes %OMABAKUP must have administrative user status n the SAS Metadata Server, as well as full perating system access t the Metadata Server directry, the rpsmgr directry, and all repsitry and backup directries. The user ID shuld als be cmpatible with the wner f the repsitry files. Typically, yu shuld use the installatin user ID. If yu need t restre files later, the metadata server prcess user ID will need t have access t the files. Nte: The %OMABAKUP macr des nt back up SAS Metadata Server cnfiguratin files such as: macnfig.xml adminusers.txt trustedusers.txt repsitry audit trails Yu must include these files as part f a full backup r full restre. Use perating-system cmmands r a third-party backup slutin t back up these files. Because the SAS Metadata Server must be paused, SAS applicatins will nt be able t access metadata during the backup prcess. T minimize the dwn time f the metadata server, yu can use a third-party tl that can take a quick snapsht f the metadata repsitries instead f using the %OMABAKUP macr. The steps t fllw are: Use PROC METAOPERATE t pause the repsitries t an ffline state. Snapsht the metadata repsitries. Use PROC METAOPERATE t resume the metadata repsitries. Back up the snapsht after the SAS Metadata Server is back nline. Fr an example, the VxFS file system in HP-UX prvides a mechanism fr taking snapsht images f munted file systems, which is useful fr making backups. The snapsht is an exact image f the file system at the time the snapsht is made. Selected files can be backed up frm the snapsht (by using standard utilities such as cpi r cp) r the entire file system image can be backed up (by using the vxdump r fscat utilities). By making a file system that nly cntains the 8

13 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm SAS Metadata Server backup files, yu can quickly take a snapsht f this file system fr archiving and maintain the maximum up time fr the SAS Metadata Server. Fr strage area netwrk (SAN) users, making a snapsht f the data t a spare area n the SAN is a way t ensure that the backup prcess happens quickly and minimizes the dwn time f the SAS Metadata Server. The backup f the data can then be dne after the SAS Metadata Server is re-started. The tradeff, if yu use this technique, is that yu need enugh extra disk space t supprt the secnd cpy f the SAS data stre. Changing the State f the Metadata Repsitry After running the %OMABAKUP macr, the repsitries may be returned t an active state. Hwever, yu must cntinue t restrict access t the metadata in rder t back up webdav and physical cntent befre returning t an active state. Yu can change the state f the metadata repsitries t be read-nly, s that client applicatins can still surface cntent but cannt edit r create new metadata. A SAS Metadata Repsitry can exist in ne f three mdes: full access, read-nly, and ffline. A repsitry s intended access mde is set when the repsitry is created and is recrded in the repsitry s Access attribute. Fr example, if a repsitry was cnfigured t be read-nly at creatin, then it will have an Access value f OMS_READONLY. The default access mde is full access. A repsitry s access mde can be temprarily changed t a mre restrictive state by issuing a Pause actin using PROC METAOPERATE. Fr example, a repsitry that was created with an access mde f full access can be paused t a read-nly r ffline state. A repsitry that was created with an access mde f read-nly can be paused t an ffline state; it cannt be paused t full access. The fllwing SAS cde example cnnects t a metadata server and issues a PAUSE actin t change client activity n all repsitries and change the repsitry manager t a READONLY state. The State parameter is mitted frm the ptins string because the default value fr the Pause state is READONLY. PROC METAOPERATE SERVER="machine.us.cmpany.cm" PORT=8561 USERID="myuserid" PASSWORD="mypasswrd" PROTOCOL=BRIDGE RUN; ACTION=PAUSE OPTIONS="<Repsitry Id=""ALL""/> <Repsitry Id=""REPOSMGR""/>" NOAUTOPAUSE; 9

14 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm The metadata server cnnectin ptins can be handled via parameters, s that yu d nt have t hard-cde the values int yur prgram. Mre infrmatin abut PROC METAOPERATE is available in nline dcumentatin at: supprt.sas.cm/nlinedc/913/getdc/en/maref.hlp/prcmetaserver.htm Backing Up WebDAV A webdav stre cntains the cntent that is used in Web applicatins. SAS Web Reprt Studi and SAS Infrmatin Delivery Prtal use a webdav server t stre cntent. Yu shuld back up the webdav stre whenever yu back up the metadata server t keep the cntent in synch. The SAS 9 platfrm supprts tw webdav prviders: Apache Grup and Xyths. The Apache webdav stre is straightfrward; it uses standard file system supprt. Yu can use system tls t back up the files. SAS can als prvide a webdav dump utility (similar t the WFSDump utility discussed later). If yu want access t this utility, cntact SAS Technical Supprt. The Xyths WFS webdav architecture uses a relatinal database and the file system, and bth cmpnents must be backed up. Yur backup and recvery strategy will vary depending n the number f Dcument Stres being used, as well as, whether External Strage is enabled. Fr a discussin f backup and recvery cnsideratins, see the "Database Recvery Guide", which is bundled in the installatin: WFS 4.0: <xyths_hme>wfs-4.0.x/dc/wfs_dbrecvery.html WFS 4.1: <xyths_hme>wfs-4.1.x/dc/en/wfs_admin.html#_db_recvery WFS 4.2: <xyths_hme>wfs- 4.2.x/dc/en/wfs_admin_file_system.html#_backup_restre File System The file system cmpnent is a set f files written t disk. This disk can be a netwrk attached strage (NAS), a strage area netwrk (SAN), r directly attached. Yu can use perating-system cmmands r third-party tls t back up the series f file systems that are used by Xyths WFS. Xyths WFS adds a temprary strage area that wrks much like a database red lg: when a file is added t the system, the file is written t its primary disk and a temprary disk. If the primary disk crashes, a sysadmin can restre the primary disk using a backup. After restratin, Xyths WFS will mve the files that are missing (files that were written after the backup but befre the primary disk crash) frm the temprary strage t the primary strage. The temprary strage is emptied n a time schedule that crrespnds t yur file system backup schedule. In this way, bth the database and the file system can always be restred t the same pint in time f any system crash. 10

15 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Relatinal Database fr Xyths Because Xyths leverages a transactinal database (pstgres, SQL Server, DB2, r Oracle), the transactinal database can be cnfigured t prvide backups and replay lgs. If the database crashes, it can be recvered by replaying the lgs and safely recnstructing the database frm a backup t the time it was last running. If external strage is nt being used, fllw the database sftware instructins t recver frm a database crash. External Strage Backup All files in the WFS system are stred in ne r mre Dcument Stres. If external strage is being used, each dcument stre writes files acrss bth a database and file system(s) (external strage lcatins). The file metadata (name, lcatin, permissins, and s n) are stred in the database while the file cntents (bytes, blbs, and s n) are stred n external strage lcatins. Bth f these systems must be backed up. If external strage is being used, use f the database as an intermediary still guarantees that the file bdies can be recvered with the same reliability. Xyths recmmends taking advantage f the tw strage lcatins that are available per Dcument Stre when cnfiguring yur backup strategy. In rder t reduce the amunt f data in the database, Xyths recmmends cnfiguring bth primary strage (the Strage Lcatin parameter n the Dcument Stre administrative page) and temprary strage as external strage lcatins. The primary strage lcatin shuld be backed up at sme interval. The amunt f time between backups f the primary strage lcatin drives hw lng files shuld be kept in the temprary strage lcatin (Temprary Strage Perid). The Temprary Strage Perid, which is cnfigured n the strage page f the Xyths WFS Admin, shuld be abut twice yur primary strage backup interval. If yu have a crash n primary strage, yu can recver the primary strage t its mst recent backup, and then use the External Strage Recvery feature in the Xyths WFS Admin t replay the files that were written since the last primary backup and the time f the crash. IE files are mved frm yur temprary strage t the primary. The temprary strage lcatin acts as yur "red/recvery" buffer and captures new file cntent that hasn't been backed up yet. WFSDump Utility SAS als prvides a WFSDump utility, which can be fund in the Xyths install directry (<xyths_hme>/custm/bin). This utility requires that the SAS Metadata Server be available t respnd t requests. Yu can pause the metadata repsitries t a read-nly state (as discussed earlier) t prevent any cntent frm being mdified r added during the backup prcess. The WFSDump utility is primarily used t migrate cntent frm ne webdav server t anther. Hwever, yu can use the same utility t prvide backups. The utility creates an XML file that describes the cntent and ne file fr every cntent resurce that is fund in the server. The files that are created by the WFSDump utility will prbably be a little larger than the database and file strage lcatin backup. 11

16 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Backing Up Physical Cntent Because SAS als leverages physical cntent that is stred n the file system, yur backup strategy shuld include the fllwing infrmatin: surce cde files fr stred prcesses and stred prcess results that are stred in permanent packages packages that have been published t a channel s persistent stre lcatin (if using the file system r FTP lcatin) data surces, including the fllwing: SAS data files, such as SAS data sets, SAS catalgs, and OLAP structure files SAS Scalable Perfrmance Data Server data relatinal database sets XML files and XML maps that are cntained in libraries custm cde, prcesses, and pst-prcesses that are assciated with SAS Data Integratin Studi jbs surce files fr SAS Data Integratin Studi jbs that have been scheduled r deplyed fr scheduling, which culd include the wrk area fr Platfrm Cmputing Prcess Manager sftware. generated and user-written SAS cde, reprts, sample and wrk data sets, and prject prperties fr SAS Enterprise Miner mdels These physical cntent files are stred as standard perating system files. Yu can use perating-system cmmands r third-party tls t back up these files. Yu shuld ensure that all in-memry changes have been flushed t disk befre perfrming backups. Yu can d this by issuing a sync cmmand, which is supprted by bth Windws and UNIX envirnments. Cnsideratins fr SAS Data Files SAS data files, such as SAS data sets and OLAP data files are lcked if there is an active server prcess that is accessing them. In rder t back up these files, yu must stp the SAS prcesses. This may require stpping all applicatin servers befre starting the backup prcess, which includes Wrkspace Servers, Stred Prcess Servers, and OLAP Servers. Once these files are available, they can be backed up using standard backup tls. 12

17 Backing Up SAS Cntent In Yur SAS 9 Enterprise Intelligence Platfrm Cnsideratins fr SAS Scalable Perfrmance Data Server The SAS Scalable Perfrmance Data Server (SAS SPD Server) tables can be backed up using standard backup tls and integrated int existing backup prcesses. Full backups are recmmended if the SPD Server data is partitined, as restratin time wuld be fairly quick. Hwever, if the data tables are large, an incremental backup strategy may be mre efficient. SAS SPD Server als prvides backup and restre utilities t alleviate resurce prblems that are assciated with backing up large data tables. Instead f backing up the entire table, the utility backs up nly the recrds that changed after the previus table backup date. Fr mre details abut backing up yur SAS SPD Server tables, see the SAS Scalable Perfrmance Data Server: Administratr s Guide (Secnd Editin) (SAS 2006). Cnclusin T safeguard yur investment in develping SAS cntent, it is imperative t establish a clear strategy t manage backups f cntent. Because backups must entail metadata, webdav cntent, and physical cntent, yu must have a crdinated prcess t handle all cmpnents. T maintain the integrity f the backups, yu must retain existing dependencies and crssreferences. The fcus f this paper is dealing with a single metadata server cnfiguratin. With mre cmplex envirnments that invlve multiple metadata servers and 24x7 service level requirements, there are additinal cnsideratins that are beynd the scpe f this paper. If yu wuld like t have mre detailed discussins abut hw t manage backups in a mre cmplex envirnment, please cntact SAS Cnsulting Services. With a cmbinatin f system tls, SAS tls, and internal prcesses, yu can establish a slid strategy fr backing up SAS cntent. These backups can be used fr auditing and recvery purpses if a system failure ccurs that requires re-staging the envirnment. Althugh we d nt discuss recvery in this paper (there will be a paper abut recvery frthcming), many f the tls that are discussed here prvide facilities fr recvery as well. See the prduct dcumentatin fr details abut this functinality. References SAS Institute Inc SAS Intelligence Platfrm: Administratin Guide, Fifth Editin. Available at supprt.sas.cm/dcumentatin/cnfiguratin/bicag.pdf. 2 SAS Institute Inc SAS Intelligence Platfrm: Overview. Available at supprt.sas.cm/dcumentatin/cnfiguratin/biv.pdf. SAS Institute Inc SAS Scalable Perfrmance Data Server 4.4: Administratr s Guide. Available at supprt.sas.cm/dcumentatin/nlinedc/91pdf/sasdc_913/scalable_ag_9719.pdf. 2 In Nvember 2006, the guide will be called SAS Intelligence Platfrm: System Administratin Guide 13

18 SAS INSTITUTE INC. WORLD HEADQUARTERS U.S. & CANADA SALES SAS INTERNATIONAL SAS and all ther SAS Institute Inc. prduct r service names are registered trademarks r trademarks f SAS Institute Inc.in the USA and ther cuntries. indicates USA registratin. Other brand and prduct names are trademarks f their respective cmpanies. Cpyright 2006, SAS Institute Inc. All rights reserved