CS-MARS Archiving procedure

Got a customer with a CS-MARS-100E-K9 appliance, and we're looking at the archiving procedure on the device in order to back it up in case of future disaster recovery.
The limited documentation I can find seems to contradict itself, where in one place it says that the default archive/restore will also archive the OS as well as all config and dynamic data (implying that it is basically a disk image of the appliance), yet in another says that I'll need to re-image to the version of software that the data comes from before I can restore anything. Can anyone clear up the following:
1 - Does the archive procedure essentially run like a disk-image backup, where re-running the pnrestore will bring a blank appliance back up to (for example) version 4.2.2 with all the config and dynamic data present?
or
2 - Will I need to reinstall up to version 4.2.2 and then run the pnrestore?
Thanks in advance.

The documentation pertaining to the pnrestore functionality is indeed horrible, but I've never really questioned that aspect of it.
At least certain parts of the archived data (the raw events and sessions) appear to be some sort of sql export. They are compressed text files. I would guess that the other database related information is not a disk image either, there are many files. The OS info might be, but I'm not sure it matters.
I have used pnrestore a couple times and it appears that all the work is done and then the system is rebooted. To me this would imply that the version of pnrestore being used is critical to the process. Trying to use the pnrestore that came with 3.x to restore 4.x data doesn't seem likely to succeed. If you're going to try it, I would be sure to get Cisco's input because even if it works in the current version, it may not 3 versions from now when you need it.

Similar Messages

  • ARCHIVEING PROCEDURE for material master

    Hi
    I have some blocked matrial in our production system..i want archive the all material whhich have blocked.. pls guide me any one to archive procedure for material deletion
    regards
    sesidahr

    > Kindly Read the Rules and Use the Search
    Once Material is Flagged you Need to Archive the Material Master Records thru Archiving Program SARA Trxn code with Archiving Object MM_MATNR
    Please Go thru the link for Details :
    http://www.sap-img.com/bc003.htm

  • Archiving procedure

    Hi,
    Can you give me the procedure of archiving script output?
    Thanks & Regards,
    Seshagiri.M.
    Intelligroup.

    Hi Seshagiri,
    Please check the following links, that may help you.
    <a href="http://www.thespot4sap.com/Articles/Archiving.asp">Archive1</a>
    <a href="http://www.planetsap.com/Archiving_solutions.htm">Archive 2</a>
    <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/d6/0db875494511d182b70000e829fbfe/frameset.htm">SAP</a>
    Hope This Info Helps YOU.
    <i>Reward Points If It Helps YOU.</i>
    Regards,
    Raghav

  • Data archiving procedure

    Dear all,
    10.2.0.4 on solaris 10
    Our Production database is 4.5TB in size and we have Tier level storage implemented in our environment.In order to reduce costs , and to avoid procuring
    new tier 1 disks ,we are planning to move some old data (huge) to one more server (database) which is attached to tier 3 storage.Some tables are partitioned and many non-partitioned too.
    Now am moving (archiving) the data between the servers using datapump or using normal insert statements accessing across db link. We are planning to get the incremental data load in every 6 months .
    Is there any other way of doing this ?. Any other way of getting the incremental data with out using inserts ?.Just a small hint or pointers will of great help
    Thanks
    Kai

    Thanks ,
    How will you define date range against the data ? Is it across the entire db or only few tables ? Any partitioned tables ?One table is partitioned. Data segregation in other tables done through date columns.
    Kai

  • Batch archiveing procedure issues

    Hi
    I am trying to archive Material batches ...but i have structued in process
    i have followed below steps:
    i have maintained varient in mm74 t.code ... then click on start button ..click on immediately ..its become green ..then click  on spool button it becomes green ..then click on execute.....and go to sm37 ... i checked job statues is finished ...
    then goto SARA t.code .. there i  entered  archive object MM_SPSTOCK..then click on archive delete button ...archive selection screen appreard ..but inthis screen .. i have got the selections (which i have created variant in MM74)
    could you pls guide ..correct process..
    Regards
    Sasi

    ......i checked job statues is finished
    this is certainly not enough, An archving job finishes even it has not archived anything because of errors
    You have to display the spoolfile with the detailed archiving  log.
    There you can see if records got archivied or not.
    and if not, SAP lists the reasons.
    In case of batches it is usually a dependency, e.g. that you have stock, or that the batch is in use, because it is referenced in purchase order, production orders, deliveries etc. Those objects have to be archived prior to the batches.
    Further, depending on customizing, the write job and the delete job can be tight together. In this case you dont need to execute the delete job manually in SARA. However, you would see an extra delete job in the job overview (but only if the write job archived something)

  • CS-MARS archiving in case of NFS crash

    Hi, is it a way to force the NFS archiving rebuild in case of NFS crash ?
    Eventually in developing status ?
    thank you in advance
    greatings
    RS

    So you lost all your data in the NFS archive? I don't believe there is a way to have it completely rebuild because some of the dynamic data is probably already FIFO'd from the database. I have noticed in the past (don't recall the exact particulars) that when I restarted archiving it went back a little bit. You might try disabling archiving, adding a couple days to the days to keep, and then restarting.

  • Archiving of spool requests (ERS documents) Apprentice Project HELP needed..

    Hi guys,
    I'm an apprentice from Germany and I have to do a project for my final exams. I could desparetly Need some help on getting started.
    In our SRM, we have a program for the Generation of ERS documents (credit note?).
    Firstly, the Programm BBPERS creates ERS Idocs on Basis of stock-receipt (?). Secondly, the program RSPPFPROCESS sends the ERS invoice to the supplier via mail.
    The document is saved only as an email.
    We do have a Z-Programm, ZZBBPERS, that is used for subsequent creation of ERS documents as PDFs. These are saved in the Spool, but for each invoice a different spool number is created.
    Now my Task is to find a way to Archive these ERS documents into an external Archive. We use d.3 as Archive, I don't know if you have heard of it. But that shouldn't matter right now.
    So the question is, how can this be achieved? I don't really know anything about archiving in SAP. And this is a very Special case. Where do I have to start? Do I Need to write a program, or can I use some of SAPs Standard possiblities? What programs are there for archiving spools? Can they be defined as only archiving Spools from program X? Where do I define archiving procedures?
    I hope some of you can get me started. I don't Need a perfect solution right off the bat, just a place to start and ideas how to Approach this Project.
    Thanks SO MUCH in advance for any help!
    Greetings,
    Sebastian

    Thank you so much, this brought me a leap Forward.
    So the Business object should be the BUS2207, right? This is our Business object for ERS. We don't have BUS2081, what is that?
    edit: Wait, what is the difference between Business Object and Archiving Object? We do not have an archiving object vor ERS.
    To clarify: We do not book in SRM, we are sending it per Idoc to another SAP System where the booking takes place.
    We are just creating the PDF out of the BUS2207 and sending it to the vendor via RSPPFPROCESS and Action "BBP_ERS".
    Can you tell me where I can see detailed Information for the Archive Connection? I have the entry in OAC0 with IP address and all. But we have no records of ever archiving in this System so how can I see Connection details and test it?
    I also have to analyze if ArchiveLink is already set up and working..
    Also, where do I define how the files are saved in the storage System? With this I mean like in which Content repositories / Folders and so on they are saved.
    What Information are given to the PDF? All document informations, like Dates invoice number and so on? How can I use them for my Archive structure?
    Thanks in advance.

  • How to archive "sent" mail to external hard drive

    Accumulated and overload of "sent" mail and would like to archive them all  (including attachments) on my external hard drive. Would someone give me the steps to do this, as a regular archiving procedure, as done with a mailbox, did not work.  Thank you.

    You can navigate to your Sent (mailbox) folder and drag and drop it to another drive.
    First remember how many messages there are in the Sent folder.
    Then navigate as follows to get to the folder:
    Users / yourself / Library / Mail.
    At this point you will see a number of folders. Look for the one that identifies your service. Something like: POP-yourname, ....
    In that folder look for Sent Messages.mbox. In there look for a folder called messages. That's where all the sent messages reside. Verify the number of messages there agrees with the number you originally noted. That is to confirm you have indeed found the correct folder.
    This, like any other folder, can be copied to an external drive, or whatever.
    The problem with this process is that each time you do it, you will be copying over a bunch of mails that have already been copied.
    Note that all of the above is on the assumption that you are running OS 10.6.8.

  • Archiving - removal of deletion indicator on p.o. item line

    Hi all,
    we've run into some problems in 4.7 with old p.o.'s which have been delete marked of the archiving program (step 1 - residence time one), where the user now want's to remove the deletion mark again, - but this is not possible, as the purch. req. has already been archived :o(
    Example:
    Purchase orders have a residence time as follows:      
    Residence time 1:       30 days
    Residence time 2:       395 days
    Purchase requisitions have a residence time as follows:
    Residence time 1:       30 days (we're having a one step archiving procedure for MM_EBAN)
    Now the p.o. has got a delete mark on item line according to residence time 1 = 30 days (MM_EKKO) and afterwards the purch. req. has been archived (according to residence time 1 = 30 days (MM_EKKO). The user can't manually remove the deletion mark from the p.o. item line again, because of an error saying "purchase requisition xxx, item xxx does not exist"
    What can we do, to remove the delete mark from the p.o. item line again - can the link between the p.o. and the archived purch. req. be removed ?
    Thanks in advance for your reply :o)
    Best regards/Med venlig hilsen
    Ulla Köhler Hansen
    Application Consultant, SAP R/3 - SRM/PLM Solutions
    The Danfoss Group
    Danfoss Information Technology
    Loc. 1.0.53
    Ellegaardvej 25 A
    DK-6400 Sønderborg
    Denmark
    Tel.: + 45 7488 3913
    Fax: + 45 7488 4715
    e-mail: [email protected]
    http://www.danfoss.com/
    This message and any files transmitted with it may be confidential and are intended only for
    the individual named. If you are not the named addressee you should not disseminate, distribute
    or copy this e-mail. Please notify the sender immediately by e-mail if you have received
    this e-mail by mistake and delete this e-mail from your system.

    Hi
    I have made the change in your code , try this code .
    it_bapimepoitem-po_item = '00100'.
    *it_bapimepoitemx-po_item = 'X'.*
    it_bapimepoitem-DELETE_IND = ' '.
    it_bapimepoitemx-DELETE_IND = 'X'.
    APPEND it_bapimepoitem.
    APPEND it_bapimepoitemx.
    Hope it will help you .
    Regards
    Rahul

  • Document not found. Excise posting not done or document is archived.

    Hi,
    I have created an order, delivery and billing document. Billing doc has been released to accounting. However though the accounting doc has been generated, the excise invoice is not generated and also BED, EDCESS & VAT amount not disable. When I was doing the Excise invoice (T code: j1iin) I got the following error
    Modvat utilization done already for XXXXXX of Delivery No: XXXXX
    Message no. 8I446
    Diagnosis
      Modvat utilization done already for mentioned billing document
    Procedure
      Check the billing document entered
    If I click on display button after that I got error like
    Document not found. Excise posting not done or document is archived.
    Message no. 8I301
    Diagnosis
    The entered document number could not be found either because it is not
    correct or the document has been archived
    Procedure
    Please check the entered document number
    Plz help me what cud be the reason for that.
    Regards
    LVK

    Dear LVK
    Go to SE16, input Table J_1IEXCHDR and execute.  There input the excise invoice number and execute.  Check whether system is showing a document.  Alternatively, without giving any data in the above table, just give the excise invoice date and execute.  Check whether the said  excise invoice is stored in the table.
    thanks
    G. Lakshmipathi

  • Would you like help me regarding archiving please .. ?

    Dear All,
    We're in the archiving project ..
    We here have scenario to reload/restore archived data from BW Production to BW Development server ...
    I did try it: I moved the archived file to archived known storage in BW Development, but it didn't recognize it ..
    My questions:
    1. Is it possible to get the scenario be done ??? How can i make it ??
    2. I run t-code AOBJ and found that there is reload program (e.g. of the program: SBOOKL), What is it for ?? Could this program solve my case above ??
    Really need ur guidances all.
    Best regards,
    Niel.

    Data Archiving
    Data Archiving u2013 a service provided by SAP u2013 removes mass data that the system no longer needs online, but which must still be accessible at a later date if required, from the database.
    Data Archiving removes from the database application data from closed business transactions that are no longer relevant for the operational business. The archived data is stored in archive files that can be accessed by the system in read-only mode.
    The following graphic illustrates the archiving process:
    Reasons for Archiving
    There are both technical and legal reasons for archiving application data. Data Archiving:
    Resolves memory space and performance problems caused by large volumes of transaction data
    Ensures that data growth remains moderate so that the database remains manageable in the long term
    Ensures that companies can meet the legal requirements for data storage in a cost-efficient manner
    Ensures that data can be reused at a later date, for example, in new product development
    Data Archiving Requirements
    Data archiving is intended to do more than simply save the contents of database tables. Data archiving must also take the following requirements into consideration:
    Hardware independence
    Release dependence
    Data Dependencies
    Enterprise and business structure
    Optical Archiving
    The term u201Coptical archivingu201D generally describes the electronic storage and management of documents in storage systems outside of the SAP Business environment. Examples of documents that can be stored in this way include:
    Scanned-in original documents, such as incoming invoices
    Outgoing documents, such as invoices created in mySAP Financials that are created electronically, then sent in printed form
    Print lists created in mySAP Business Suite
    Residence Time and Retention Periods
    The residence time is the minimum length of time that data must spend in the database before it meets the archivability criteria. Residence times can be set in application-specific Customizing.
    The retention period is the entire time that data spends in the database before it is archived. The retention period cannot be set.
    Ex: If the residence time is a month, data that has been in the system for two months will be archived. Data that is only three weeks old remains in the database.
    Backup & Restore
    Backup is a copy of the database contents that can be used in the case of a system breakdown. The aim is that as much of the database as possible can be restored to its state before the system breakdown. Backups are usually made at regular intervals according to a standard procedure (complete or incremental backup).
    Reloading the saved data into the file system is called restoring the data.
    Archiving Features
    Data Security
    Data archiving is carried out in two steps (a third step u2013 storage of archive files u2013 is optional: In the first step, the data for archiving is copied to archive files. In the second step, the data is deleted from the database. This two-step process guarantees data security if problems occur during the archiving process.
    For example, the procedure identifies network data transfer errors between the database and the archive file. If an error occurs, you can restart the archiving process at any time because the data is still either in the database or in an archive file. This means that you can usually archive parallel to the online application, that is, during normal system operation, without having to back up the database first.
    You can further increase data security if you store the archive files in an external storage system before you delete the data from the database. This guarantees that the data from the database will only be deleted after it has been securely stored in an external storage system.
    Data Compression
    During archiving, data is automatically compressed by up to a factor of 5. However, if the data to be archived is stored in cluster tables, no additional compression takes place.
    Storage Space Gained
    Increased storage space in the database and the resulting performance gains in the application programs are the most important benefits of data archiving. Therefore it is useful to know how much space the data to be archived takes up in the database. It may also help to know in advance how much space the archive files that you create will need.
    Note: - Data is compressed before it is written to the archive file. The extent of the compression depends on how much text (character fields) the object contains.
    Archiving without Backup
    With SAP Data Archiving, data can be archived independently from general backup operations on the database. However, SAP recommends that you backup archive files before storing them.
    Accessing Archived Data
    Because archived data has only been removed from the database and not from the application component itself, the data is always available. Archive management allows three types of access:
    1.     (Read) access to a single data object, such as an accounting document
    2.     Analysis of an archive file (sequential read)
    3.     Reload into the database (not possible for all archiving objects)
    Converting Old Archive Files
    When archived data is read, the system automatically makes the conversions required by hardware and software changes.
    When old archive files are accessed, the Archive Development Kit (ADK) can make allowances for changes to database structures (field types, field lengths, new fields, and deleted fields) after the data was archived and for changes to hardware-dependent storage formats. This is only done on a temporary basis during read access. The data in the archive file is not changed. The following items are changed (if necessary) during automatic conversion:
    Database table schema (new and deleted columns)
    Data type of a column
    Column length
    Code page (ASCII, EBCDIC)
    Number format (such as the use of the integer format on various hardware platforms)
    If database structures in an application have undergone more changes than the ADK can handle (for example, if fields have been moved from one table to another or if one table has been divided into several separate tables), then a program is usually provided by the relevant mySAP Business Suite solution for the permanent conversion of existing archive files.
    Link to External Storage System
    Archive files created by Data Archiving can be stored on tertiary storage media, such as WORMs, magnetic-optical disks (MO), and tapes using the SAP Content Management Infrastructure (which also contains the ArchiveLink/CMS interface). This can be done manually or automatically.
    You can also store archive files in the file system of an HSM system. The HSM system manages the archive files automatically. For storage, the HSM system can also use tertiary storage media, such as MO-disks.
    CMI/R u2013 Content Management Infrastructure / Repository
    HSM u2013 Hierarchical Storage Management Systems
    Archiving Procédure
    The basic Archiving procedure is carried out in three steps, 
    Creating the Archive Files
    Storing Archive Files
    Executing the Delete Programs 
    Security Vs Performance
    Optionally, you can store archive files after the delete phase. To do this, you must mark Delete Phase Before Storage in archiving object-specific Customizing.
    If security is your main concern, then you should not schedule the delete phase until after the archive files have been stored. In this way you know that the data will only be deleted from the database after the archive files have successfully been moved to the external storage system. In addition, you can set the system to read the data from the storage system and not from the file system.
    However, if your main concern is the performance of the archiving programs, then you should schedule the delete program first and then store the files.
    Creating Archive Files (WRITE)
    In step one, the write program creates an archive file. The data to be archived is then read from the database and is written to the archive file in the background. This process continues until one of following three events occurs:
    All the data is written to an archive file
    Archiving is not complete, but the archive file reaches the maximum size specified in archiving object-specific Customizing
    The archiving is not yet finished, but the archive file contains the maximum number of data objects specified in Customizing.
    If in cases 2 and 3 there is still data to be archived, the system will create another archiving file.
    Storing Archive Files (STORE)
    Once the write program has finished creating archive files, these can be stored. There are several ways of storing archive files:
    Storage Systems:
    If a storage system is connected to mySAP Business Suite: At the end of a successful write job, a request is sent to this system to store the new archive files (provided the appropriate settings were made in Archiving Object-Specific Customizing. You can also store archive files manually at a later point if you do not want them to be stored automatically. Storage is carried out by the SAP Content Management Infrastructure (which contains the ArchiveLink/CMS interface).
    HSM Systems:
    If you use an HSM system, it is sufficient to maintain the file name in Customizing (Transaction FILE). You do not then need to communicate with the storage system using the SAP Content Management Infrastructure, because the HSM system stores the files on suitable storage media according to access frequency and storage space.
    Existing Storage Media:
    Once the delete program has processed the relevant archive file, you can manually copy archive files to tape.
    Running Delete Programs
    After closing the first archive file, the archive management system creates a new archive file and continues with the archiving process. While this happens, another program reads the archived data from the completed archive file and deletes it from the database. This procedure guarantees that only data that has been correctly saved in the archive file is deleted from the database.
    If you do not carry out deletion until after the data has been stored, you can make a setting in Archiving Object-Specific Customizing so that the system will read archive files the from the storage system during deletion. In this way, you can detect errors in good time which might arise when transferring or saving the archive files in the storage system.
    When the last archive file is closed, a delete program starts to run for this file. The graphic shows that several delete programs are running simultaneously for previously created archive files. Because, unlike the delete program, the write program does not generally carry out any transactions that change data in the transactions, the write program creates new archive files faster than they can be processed by the delete program. This decreases the total archiving runtime because the database is used more efficiently.
    Note:-
    Scheduling the Archive jobs outside SARA
    WRITE:-
    Using an external job scheduler (SM36, SM62)
    WRITE Run followed by EVENT - SAP_ARCHIVING_WRITE_FINISHED,
    Parameter is Session Number
    To analyze the archiving information of a particular session, use FM
         ARCHIVE_GET_FILES_OF_SESSION
         Input is Session Number
    DELETE:-
    Using an external job scheduler (SM36, SM62)
    Using program RSARCHD, input u2013 Obj Name, Max. no. of files, Max no. of sessions, Max no. of jobs,
              Background User
    DELETE run followed by EVENT - SAP_ARCHIVING_DELETE_FINISHED
         Parameter is Session Number
    To analyze the archiving information of a particular session, use FM
         ARCHIVE_GET_FILES_OF_SESSION
         Input is Session Number
    Archiving Object
    The archiving object is a central component of SAP Data Archiving. The archiving object specifies precisely which data is archived and how. It describes which database objects must be handled together as a single business object and interprets the data irrespective of the technical specifications at the time of archiving (such as release and hardware).
    Note:-
         An archiving object has a name of up to ten characters in length.
         Transaction code to maintain the Archiving Object is AOBJ.
    The following programs must (or can) be assigned to an archiving object. The SAP System contains programs (some of which are optional) for the following actions:
    Preprocessing (Optional)
    Some archiving objects require a preprocessing program that prepares the data for archiving. This preprocessing program marks data to be archived, but it does not delete any data from the database. Preprocessing programs must always be scheduled manually and are run from Archive Administration.
    Write
    This program creates archive files and writes data to them. At this point, however, no data is being deleted from the database.
    You can specify in archiving object-specific Customizing whether the next phase (delete) is to take place automatically after the archive files have been created. Delete jobs can also be event-triggered. To do this, you set up the trigger event in archiving object-specific Customizing.
    Delete
    This function can entail several activities. The activities are always dependent on the existing archive files. Normally, the data is deleted from the data base. However, in some case, the archived data in the database may only have a delete indicator.
    In archiving object-specific Customizing, you can specify that archive files, after successful processing, are to be transferred to an external storage system using the SAP Content Management Infrastructure (which contains the ArchiveLink/CSM interface).
    Postprocessing (Optional)
    This function is usually carried out after deletion has taken place. It is not available for all archiving objects. If the data has not yet been deleted from the database by the delete program, it is deleted by the postprocessing program.
    Reload Archive (Optional)
    You can reload archived data from the archive files into the database using this function. It is not available for all archiving objects. To access this function, choose Goto ® Reload.
    Index (Optional)
    This function builds (or deletes) an index that allows individual access. It is not included in every archiving object.
    Data Object
    A data object is the application-specific instance of an archiving object, that is, an archiving object filled with concrete application data. The Archive Development Kit (ADK) ensures that data objects are written sequentially to an archive file. All data objects in an archive file have the same structure, which is described in the archiving object.
    Archive Administration (SARA)
    All interaction relating to data archiving takes place in the Archive Administration (transaction SARA). Features of Archive Administration:
    Preprocessing
         Write
         Delete
         Postprocessing
         Read - Enables you to schedule and run a program that reads and analyzes archived data.
         Index
         Storage System - Enables archive files to be transferred to a connected storage system and  
                                             enables stored archive files to be retrieved from a storage system. 
         Management - Offers an overview of archiving sessions for one archiving object.
    Depending on the action you have selected, you can use Goto on the menu to access the following menu options:
         Network Graphic
         Reload
         Customizing
         Job Overview
         Management
         Stored Files
         Database Tables
         Infosystems
         Statistics
         Interrupting and Continuing
    Archive Development Kit
    The Archive Development Kit (ADK) is a tool for developing archiving solutions. It also prepares the runtime environment for archiving. From a technical viewpoint, it is an intermediate layer between the application program and the archive that provides all the functions required for archiving data.
    The ADK functions are required for archiving and for subsequent access to archived data. The ADK automatically performs the hardware-dependent adjustments (such as code page and number format) and structural changes that are required when archive files are created. When the archive files are accessed later, the ADK temporarily converts data that was archived using earlier SAP releases.
    Note:-
    S_ARCHIVE is the SAP delivered user authorization check object over archiving objects. The Archive Development Kit (ADK) performs the check when an archive file is opened for one of the following actions:
    Write
    Delete
    Read
    Reload
    Database Tables in Archive Administration (DB15)
    This enables you to display all of the tables for a specific archiving object and as well as allows to display the list of Archiving Objects on a particular database table. Also enables to display the storage and space statistics. This also provides further information, such as the time and number of the last archiving session and various details on the client used.
    Network Graphic
    You can use the network graphic to show any existing dependencies between archiving objects. It shows business process flows and contexts that can influence the archiving sequence. In particular, at the start of an archiving object, you can use the network graphic to obtain a good overview of related documents.
    In an archiving session, you must take into account any dependencies between archiving objects that require a specific archiving sequence. In general, you cannot archive data for an archiving object that has preceding objects until these preceding objects have been archived.
    You can use the network graphic to determine whether the archiving object that you want to use has preceding objects. If so, the preceding objects should be implemented before the current archiving object. The nodes in the network graphic represent the archiving objects. A node displays the following information:
    Archive Object Name
    Application Component Name
    Short Description
    Date of last archiving
    Status of the session
         If status is u2018Greenu2019
         Archiving and Deletion is Successful
         If status is u2018Yellowu2019
         Successfully archived, but not yet deleted, or Archiving still running, or Delete in progress or
    Delete Cancelled
    If status is u2018Redu2019
    Not yet archived, or Archiving cancelled
    Standard Log (Spool List)
    During archiving, a log is usually generated. This can be done during the write, delete, read, or reload phases. This is usually in the form of a standard log. In some cases, an application-specific log may be generated.  Depending on the archiving action that was carried out, the standard log contains statistical information per archiving session or archive file according to the following categories:
    Archiving session number
    Number of data objects for processing
    Archive session size in megabytes
    Total header data in %
    Table space in MB occupied for:
              Tables
              Indexes
    Number of table entries processed
    You can call the standard log from the screen Archive Administration: Overview of Archiving Sessions. Choose Spool List.
    Accessing Archived Data
    Data that was archived using SAP Data Archiving has been relocated from the database but not placed beyond the application. Data is still available for read access and analysis. In some cases, archived data can even be reloaded into the database.
    Note:-
    A prerequisite of read access and reload access, is that the file can be found in the file system.
    Three types of access are possible:
    (Read) access to a single data object, such as an accounting document
    Direct access or single document access requires an index that can be built either during archiving or at a later point. A complex search of the documents stored in the archive files, in which all orders of an article in a particular batch are required for a product recall action, is not possible.
    The Archive Information System (AS) supports direct access using archive information structures that can be generated automatically either when the archive files are being written, or at a later point.
    Analysis of an archive file (sequential read)
    It is possible to run an analysis for one or several archiving sessions. The results of the analyzed data objects are displayed in a list. Furthermore, some archiving objects offer the option of a combined analysis. With this option, you can link current data in the database and archived data.
    Reloading into the database
    Archived data does not usually need to be reloaded because it remains accessible by the applications. There is also a lot of data that cannot be reloaded or for which reloading is problematic. For this reason, reload programs do not exist for all archiving objects.
    Archiving Session Overview
    On this screen, you can display and edit management information on archiving sessions. One archiving session is equal to Write and Delete jobs.  Within a status area, archiving sessions are, by default, organized in groups of 20. The sessions are ordered according to different status.
    Interrupting and Continuing
    In order that Data Archiving can be seemlessly integrated into the production system, you can interrupt an archiving session during the write phase and contine it at a later time. This enables you to react, during archiving, to specific time constraints or hard-disk space shortages. You can continue and complete interrupted archiving sessions when you have more time or more storage space. 
    To interrupt an archiving session:
    The archiving object must be registered in transaction AOBJ as interruptible, otherwise the Archive Development Kit (ADK) is unable to inform the write program of the interruption request.
    The write program must be able to process the interruption request.
    The archiving session must be run in production mode (not test mode) and be in process.
    The delete phase must be able to start before the write phase has finished (setting in transaction AOBJ).
    To continue an archiving session:
    The session must have been interrupted within the context of the interrupution concept. Archiving sessions that were interrupted for other reasons or that were terminated by archive management cannot be continued.
    The delete phase must have completed for the data that was archivied up to the point of interruption, that is, the archiving session must have the status completed.
    Database Action Before and After Archiving
    Archiving uses application software that depends on and affects the organization of the database data. You should therefore organize the database before and after archiving.
    Before Archiving
    Archiving application data helps to prevent storage and performance bottlenecks. Since relocating data can, in some circumstances, in itself, impair performance u2013 this is the case if you need to access archived data u2013 you need to consider carefully what data to archive. To determine whether or not you should archive data, consider the following questions:
    If there are memory problems, can more memory be assigned to the table?
    How likely is it that you will need to access the archived data again? How often?
    Is the data accessed using an optimal index?
    Does the application perform a full table scan on the tables that contain the data to be archived?
    After Archiving
    Reorganize index: If data has been archived or simply deleted and the associated tables were accessed via an index, the index should be reorganized. Deleting table entries leaves holes in the table which are still indexed. Reorganization can shorten the access paths, reducing response times.
    Update the database statistics: If your database uses a cost-based optimizer, you must choose Update Statistics to recalculate the access paths.
    Reorganize tablespace or database space: Whether you should reorganize the tablespace depends on the reason for archiving.
    Do you expect a lot of new data for the archived tables?
    Do you want to make space for other tables?
    Note:-
    Reorganization takes a long time and may need to be repeated after archiving. Throughput during a reorganization:
         With export/import     :           approximately. 60-100 MByte/hour.
           With unload/load     :           approximately. 250-300 MByte/hour.
    Perform an SQL Trace after reorganization.
    Statistics
    When writing, deleting, reading, or reloading, statistical data on each archiving run is automatically generated and is persistently stored in the database The data archiving administrators can analyze these figures so that they can better plan future archiving projects and request the necessary resources. Statistics also provided pertinent information on the role of data archiving in reducing the data volume in the database.
    You can call this screen directly from the Archive Administration (SARA), or using the transaction SAR_DA_STAT_ANALYSIS. It displays the following information:
         Archiving Session Number
         Archiving Object Name
         Client ID on which the archiving session was carried out
         Date on which the archiving session was carried out
         Status of the session number
         Portion of the Header data in the archiving session
         DB Space (WRITE) u2013 Virtual storage space in MB, which is occupied by an incomplete archiving                          session in the database
         DB Storage Space (DELETE) - Virtual storage space in MB, which is occupied by an incomplete                               archiving session in the database
         DB Space (Reload) u2013 Virtual storage space in MB
         Written Data Objects in an incomplete archiving session
         Deleted Data Objects for an incomplete archiving session in database
         Reloaded Data Objects
         Number of delete jobs
         Write job duration
         Delete job duration
         Reload job duration
    Logical Path and File
    Archive files are stored in the file system under a physical path and file name that is derived from a user-definable logical path or file name. The definition can be divided into the following steps:
    Definition of the logical path name
    Definition of the logical file name
    Assignment of the logical fine name for the archiving object
    By default, the system uses the logical file name ARCHIVE_DATA_FILE and the logical path name ARCHIVE GLOBAL PATH as defaults. Consequently, the names only need to be changed if they have to be adjusted to meet special requirements.
    Data Archiving Monitor
    Use this indicator to activate or deactivate the data archiving monitor (transaction SAR_SHOW_MONITOR. If you mark this checkbox before data archiving, archiving-relevant information on the write and delete jobs is updated. This information can be analyzed using the data archiving monitor. If there are errors, alerts are issued.
    The data archiving monitor offers the following information:
    Overview of all the archiving objects that have been run
    Detailed information on the individual archiving sessions
    Processing status display
    Help on analyzing open alerts

  • Archiving of PO attachments

    Hi MM Gurus,
    May I know the standard SAP Archiving procedure  for Purchase Order with attachments ( I am not talking about the business service attachments). The attachments are at the item level.
    Please help.
    Thanks
    Pranav

    Hi Pavan,
    There are standard procedure to archive attachment for PO.
    This senario is know as Document archiving, and again in this document archiving there are 2 types i.e. Late archiving and Early archiving.
    Early archiving means that you have the document for which you have to create business data (Purchase order), here you will archive the document and assign it while creating business object
    Late archiving means that you already have business data in sap system, now you have to archive the reference document and attach the same to the existing business data (PO).
    I belive yours is 2nd scenario, then you have to create Order type and assign order class it in transaction OAC2,
    Link the order type to link table and to content repository in OAC3, later perform OAD5 and then with OAWD.
    GOS will also help in attaching the document to business object.
    I know it will be difficult to understand these transaction since there are several steps involved so i advise you to refer a document which will give you information on document archiving (help.sap.com)
    Reward if it benifits.
    -Thanks,
    Ajay
    Edited by: Ajay Kumar on Apr 6, 2008 8:14 AM

  • Archiving sales orders

    Hi,
    Is it possible to archive only sales orders, or does archiving sales orders mean we have to seperately go and archive all related deliveries, billing, etc.
    Any idea??
    Thanks
    Keshi

    HI Kesineni,
    Sales order Archiving:
    In "SARA" transaction you can select the number of the sales orders that you want to archive.
    The archive procedure has two steps:
    First - you run the preparation to the archive (here the documents steel in database, is just a test to know if the documents are ready to be archive, that means, they are completed)
    Second - You run the archive process. Here, if you have a variant to eliminate the documents automatically, the documents disappear for the data base.
    SD archiving objects are:
    SD_VBAK sales orders
    RV_LIKP deliveries
    SD_VBRK billing documents
    Reward points pls.
    Regards,
    Govind.

  • While mat .doc archiving error

    Hi
    While mat .doc archiving i am getting error can not be archived due to Document
    not completed.
    How to find what are all the documents and how to correct the same ?
    Thanks
    Regards,
    Dhinesh

    Dear,
    Please go through the below:
    Archiving (transaction SARA)
    Data archiving removes bulk data which is no longer required in the System, but which must be retained accessibly, from the database. Data in the R/3 database can only be archived via archiving objects, which describe the data structure. Financial accounting documents, for example are archived via the archiving object FI_DOCUMNT, which comprises the document header, company-code-dependent postings, change documents, SAPscript texts and other elements. The application archiving objects are pre-defined in the system. The archiving programs are scheduled as background jobs, but can run during on-line processing. The system need not be shutdown.
    The archiving procedure comprises two main steps:
    Create archive files: the data to be archived are first written sequentially into a newly created file. The data then exist twice in the database. These archive files can, e.g. be passed to an archive system, via ArchiveLink.
    Execute delete program: the data in the archive files are removed from the database by the delete program.
    You can check how the archive filenames and archive destination are setup in transaction FILE
    Always remembers to check the setting before any archiving.  The settings will determine things like whether the delete programs will start automatically.  (it is not advisable to start your delete programs automatically).
    You can configure all the customizing settings with transaction AOBJ - Archive Objects.
    MM_MATBEL - Archive material document
    OMB9 - Archiving - Material document retention period.
    The default documents life is 200 days.  You need to maintain the documents life for each Plant in your company before you can start archiving.  If you did not maintain, you will get a list with 'Valid.period not maintained for tr./ev. type of doc.'.
    MM_ACCTIT - Archive accounting interface tables
    The documents store in the table are for applications which are to be supplied with the posting data at a later date of MM Inventory Management and MM Invoice Verification.
    If you are using 3.x, this archiving object might not be found. You need to import it from sapservX. Read note 89324, 99388, 83076.
    Take a look at OSS note 48009 for the detail explanation of which data is updated in the ACCT* tables.
    PP_ORDER - Archive production order
    OPJH - Production Order retention period. Maintain Retention 1 and 2.
    If your set your retention 1 and 2 as 10, that means that after 10 days of setting the delete flag then you can set the deletion indicator.  After 10 days of setting the deletion indicator then you can start archiving.  Therefore, to archive immediately, you can leave retention 1 and 2 as space.  Please take note that retention 1 and 2 act as a safety net if you happened to archive the wrong record.  You will have to decide whether to have the retention time gap or not.
    FI_DOCUMNT - Archive Financial Accounting Documents
    Maintain the account life      - transaction OBR7
    Maintain the documents life - transaction OBR8
    SD_VBRK - Archive Billing Documents
    There are no posting date or fiscal year/period selection.  You can only specify the billing documents date.  In order that you do not archive the wrong record, you have to write a ABAP query or report to print out the various billing documents number ranges you want to archive.  You can extract the data from table
    VBRK - Billing: Header Data.
    VN01 - Check all the number ranges for Billing Documents.
    Click Overview buttom or Hold the Shift key and press F7.
    RV_LIKP - Archiving Deliveries
    VORL - Maintain the retention period. Number of days which must have elapsed since the delivery was created, before the delivery can be archived.
    VLAL - Archive deliveries
    Regards,
    Syed Hussain.

  • Archiving ECM

    Hello Gurus,
    I reviwed all the PP archiving objects/tables for BOM, Workcenters, Routings, Production orders, Process orders and Backflushing. I couldn't find any information related to ECM archiving.
    Could you please let me know how Engineering Change Orders can be archived.
    We are currently using 4.6c.
    I appreciate your help.
    Thanks in advance
    Srini

    Dear Srini
    Use T-CODE : SARA  and Archiving Object :LO_CHANGEM
    SOME TIPS:
    Archiving (transaction SARA)
    Data archiving removes bulk data which is no longer required in the System, but which must be retained accessibly, from the database. Data in the R/3 database can only be archived via archiving objects, which describe the data structure.
    The archiving procedure comprises two main steps:
    Create archive files: the data to be archived are first written sequentially into a newly created file. The data then exist twice in the database. These archive files can, e.g. be passed to an archive system, via ArchiveLink.
    Execute delete program: the data in the archive files are removed from the database by the delete program.
    You can check how the archive filenames and archive destination are setup in transaction FILE
    Always remembers to check the setting before any archiving.  The settings will determine things like whether the delete programs will start automatically.  (it is not advisable to start your delete programs automatically).
    customizing settings with transaction AOBJ - ECM Object LO_CHANGEM
    Regards
    Narayana

Maybe you are looking for