Record Center Archival Strategy/Best Practise

I am familiar with record center but I would like some guidance on how to do some of the things.
Scenario : We have 4 site collections, 2 site collections are containing team sites which are built for different departments and one site collection is project site collection which contains sites for on going project and last site collection is for record
center. There are different content types associated with each of libraries in above sites.
-- From the team sites in those two site collections, only few documents from document libraries need to be archived (Here I would like to know, should I create a separate library in record center for each library in source site -- in this approach record
center will have numerous libraries or just create one library for each team site and archive all documents in it -- this approach has drawback of finding document)
Same way for project site collection where once project is ended they would like to archive all libraries : should I archive each separate library or archive all project libraries for that project into one library on record site.
Dhaval Raval

Hi Dhaval,
I found articles for different aspects of Record Management in SharePoint 2010 for your reference:
Introducing Records Management in SharePoint 2010
http://blogs.msdn.com/b/ecm/archive/2010/02/13/introducing-records-management-in-sharepoint-2010.aspx
Estimate performance and capacity requirements for large scale document repositories in SharePoint Server 2010
http://technet.microsoft.com/en-us/library/hh395916(v=office.14).aspx
Choose how to store and manage records
https://support.office.com/en-us/article/Choose-how-to-store-and-manage-records-5299e96c-00ea-47dc-a711-f21b3cea00d3?ui=en-US&rs=en-US&ad=US
To design the record management plan, we need consider about govermance, performance, security and etc.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Similar Messages

Exchange 2013 Archive mailbox best practise

Current senario:
Migrating to Exchange 2013 CU3 from lotus Domino
in lotus domino the customer is having huge archive files(nfs file size is around 30 GB, like wise users are having multiple archive file with same size.)
Requirement is all these file need to migrated to exchange 2013 CU3. whcih we are taking care by using thrid party tool.
My concern is exchang e2013 support for huge mailbox size. if so what maximum size supported for online mailbox and archive mailbox.
can I assign multiple archive mailbox to users.
we have got separate Exchange 2013 archive server in place
We would like know the best practise/guide line for archive mailbox/live mailbox size.
refered below link:
http://blogs.technet.com/b/ashwinexchange/archive/2012/12/16/major-changes-with-exchange-server-2013-part-1.aspx

The key decision is that the content in the primary mailbox is synchronized with the client when in cached mode, while the content in the archive is not. So I'd want to keep the primary mailbox populated with the content the user needs on a daily basis,
and put the rest in the archive. Unfortunately, that answer is not a number, and it isn't the same for all users.
Each user can have zero or one archive mailboxes, not multiple.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Any best practise to archive PO's which does not have corresponding invoice

Hello,
As part of initial implementation and conversion, We have a lot of PO's / LTA created but their corresponding invoices were never converted into SAP from legacy system. SAP archiving program tags those as not business complete as the invoice qty does not match with po qty (there are no invoices to start with). Just flagging 'delivery complete and final confirmation' of PO does not help. Anybody ran into similar situation and how did they resolve it? I am reluctant to enhance standard SAP archiving program to bypass those checks and that is my only last option. Any SAP recommended Note / best practise etc would help.
Satyajit Deb

Where is the invoice posted?
was the invoice posted in the legacy system?
Clearance of GR/IR account with MR11 will usually close such POs.

Best Practise for Data Archiving

Hi All,
I have query in SAP that when business will do the data archving in their R3 systems.
On which basis they will do data archiving?
Is there any minimum period that data need's to be archived?
before doing the data archiving what they will do ?
Regards
Srini

Hi Srini,
1. SAP suggestes to implement data archiving strategy as early as possible to manage database growth .
However pople think of archiving when they realise the problems like large data volumes,slow system resonse time,performance issues etc...
2. There is a proper way to implement Data Archiving . Database has to be anaylzed first for getting the top DB tables and Archiving objects.
3. Based on the DB analysis ,Data archiving plan has to be implenemted according to data management guide.
4. There is a minimum period known as residence time has to be completed before any data to be archived. Once the document is business completed and serverd its minimum required period in the Database ,it can be archived.
5, Before going for data archiving there are many steps to be followed like analysis,configuration etc that you can see in details at the link below :
http://help.sap.com/saphelp_47x200/helpdata/en/2e/9396345788c131e10000009b38f83b/frameset.htm
let me know if this helps you .
-Supriya
Edited by: Supriya Shrivastava on May 4, 2009 10:38 AM

Lifetime of document[ record] in a record center

hi all,
would like to know for how many days/ months/years we can keep document as a record in the record center site collection.
i have configured the record center and providing a link to record center to view the document.now, as per the design will i be able to access the same document[record] after few months/years.
PrasadWT

Hi Prasad,
If a document has been declared as a record in a record center, it will be a record until you undeclared it as a record.
However, the documents may not always be stored in the place where you add them.
It depends on the Content Organization Rules and Retention Policies set on the records or documents.
If such rules or policies have been created, actions will be operated on the records or documents such as moving them to another place.
You can check the Content Organization rules by going to Site settings > Content Organization rules.
You can check the Retention Policy by going to Library settings > Information management policy settings.
More references:
Records management:
http://blogs.msdn.com/b/mcsnoiwb/archive/2009/11/05/sharepoint-2010-records-management.aspx
Content Organization rules:
https://support.office.com/en-us/article/Configure-the-Content-Organizer-to-route-documents-b0875658-69bc-4f48-addb-e3c5f01f2d9a?CorrelationId=ee3c8983-fd6f-4cad-b57e-a9cc4a5d1505&ui=en-US&rs=en-US&ad=US
Retention Policy:
https://mikesnotebook.wordpress.com/2013/05/20/sharepoint-retention-policies/
Best regards.
Victoria
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Best Practises for Backup & Recovery windows

Hi All,
Could you please let me know the following .
1. Best Practises to be followed for backup & recovery on windows server 2008
2. how to plan for the DR on windows
Regards
Mohammed. Abdul Muqeet

Mohammed Abdul Muqeet wrote:
Hi All,
Could you please let me know the following .
1. Best Practises to be followed for backup & recovery on windows server 2008
As far as the Oracle database is concerned, best practices on Windows server 2008 are exactly the same as for any other OS.
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/toc.htm
(and my own prejudice, developed over 30+ years in this industry and working with Oracle on Windows beginning with Oracle 7.3 on windows 3.11, is that best practice is to stay as far away from Windows as possible)
2. how to plan for the DR on windowsAs far as the Oracle database is concerned, best practices on Windows server 2008 are exactly the same as for any other OS.
Backup everything. Get the backups off site. Perform regular DR drills. Document everything. Keep a copy of the documentation off site. (Doesn't do any good to have the DR manual located such that it gets destroyed in the same disaster that takes out your data center. ) Have an off-site DR site.
While it isn't in your lane as a DBA, you need to keep reminding managment that DR is about more than just the database, and even more than just the data center itself. If there is a physical disaster (ask the people in Oklahoma City about that ... over the years - multiple F5 tornadoes, plus a truck bomb) all kinds of infrastructure and documentation issues. What about important records (like the DR manual) that exist only in someone's desk drawer? Where are the business units going to set up shop and how are they going to connect to the restored database at the DR site?
I've seen DR manuals that got down to the detail of temporary housing for employees and how to get coffee at the DR site.
>
>
Regards
Mohammed. Abdul MuqeetEdited by: EdStevens on May 23, 2013 7:44 AM

Mapping one site collection to one record center

hi,
i would like to map one site collection to one record center
is it possible
assume , am having 10 site collections, and if i create 10 record center site collections , how can i map these 10 site collections to 10 record centers.
help is appreciated!

Hi Benjamin,
Yes, you can map one site collection to one record center. Here is the steps you can refer to:
Configure Send to locations for your Records Centers.
Allow for sending outside the site.
Create Content Organizer Rule to send to a record center for your Site Collections.
For more information, you can refer to the blog:
http://blogs.msdn.com/b/mcsnoiwb/archive/2010/03/04/route-records-to-other-site-collections.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

How to pass version number from source location to records center?

When designing our record management approach, one of the requirements from business is to pass the version number from the source location to records center. They need to know which version has been declared as a record for the same document.
Is there a way to implement this (OOB)? Thank you.

Hi,
Based on your description, my understanding is that when you sent a document to records center, you want to pass version number from source location to records center.
When a document is sent to the records Center, we keep its version number as assigned in its original document library as metadata that is submitted along with the document to the Records Center (in the “Properties” sub-folder of the document library in
the Records Center).
Automatically synchronizing that version number directly into the versioning system in the Records Center is something we should probably consider for a future version, but even in the current version we definitely don’t lose that information.
Hope this helps clarify.
Refer to the following article:
http://blogs.msdn.com/b/recman/archive/2006/08/24/715883.aspx
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Best Practise for Data Refresh & Hierarchy

Hi,
During a recent discussion with one of our BI user groups, the questions were raised as what the best practice are to handle the following two issues.
Issue 1:
If entries are posted to the prior periods in SAP R/3 (outside of the daily auto-refresh range), the current process is that the user group will ask us to conduct a manual refresh in BI for the prior periods which are effected.
Question: Is it possible to set up a trigger in the system, so that BI knows which periods are changed and automatically refreshes data for those periods?
Issue 2:
If a hierarchy used in the reports is modified, there might be an adverse impact on the financial data the user group reports. The current process we have in place is to run a group of BI reports for both current year and prior year to make sure nothing is impacted, but there is limitation to this current process. What if there is no impact on current or prior year, but on the years prior to that?
Question: What other global companies do to minimize such reporting impact, especially when they have hundreds of complex reports?
If someone has any info on this, help me in sharing the same.
Thanks all for your support.
Regards,
Murali

Hi Srini,
1. SAP suggestes to implement data archiving strategy as early as possible to manage database growth .
However pople think of archiving when they realise the problems like large data volumes,slow system resonse time,performance issues etc...
2. There is a proper way to implement Data Archiving . Database has to be anaylzed first for getting the top DB tables and Archiving objects.
3. Based on the DB analysis ,Data archiving plan has to be implenemted according to data management guide.
4. There is a minimum period known as residence time has to be completed before any data to be archived. Once the document is business completed and serverd its minimum required period in the Database ,it can be archived.
5, Before going for data archiving there are many steps to be followed like analysis,configuration etc that you can see in details at the link below :
http://help.sap.com/saphelp_47x200/helpdata/en/2e/9396345788c131e10000009b38f83b/frameset.htm
let me know if this helps you .
-Supriya
Edited by: Supriya Shrivastava on May 4, 2009 10:38 AM

Forms Library Not Working Correctly in Records Center

Greetings,
I have a scenario where I have created a form library in a records center. This form library has the same InfoPath form published to it as is in the primary collaborative site. In the collaborative site, based on certain conditions, a workflow
moves the form entry to the records center; all of this work correctly.
However, the entry in the form library is recognized as a plain XML file, this can be seen by the file type icon. When I click on the item I want it to open using the InfoPath form. Is there something special I need to do to make this work?
Thank you in advance for your suggestions!
Bob

Hi，
Based on your description, my understanding is that when you use workflow to move the form entry from collaborative site to the records center, you can't open the items in the records center using the InfoPath form.
Could you please offer how do you use workflow to move the form entry from collaborative site to the records center?
You said "However, the entry in the form library is recognized as a plain XML file". Does the items looks like the following:
You said "When I click on the item I want it to open using the InfoPath form". if the items look like the following, Then you can open the items using the InfoPath form.
I have done a test in my SharePoint, I create two new form library with the same infopath form template.
then I create a workflow "Create List Item" action to move the form entry from the first form library to the second form library. Then I can open the items from the second form library using the InfoPath form.
If I misunderstanding your issue, Please offer some screenshot about issue, I will help you better.
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]
Hi Lisa,
I use the Submit File action in SharePoint Designer to move the file.
To be able to reproduce my same issue, you would need to provision your records center in a different site collection.
I have the same InfoPath form published to the form library in the records center and have created the correct link to open the form; using formserver.aspx?XmlLocation=... However, I still can't get the item (in the records center) to open.
Bob

BEST PRACTISE on users deletions HR/SU01

Hi
we use CUA/SSO.
The records are fed from HR records and sent to Active Directory (AD)
AD brings backs the records and creates/changes users in SU01
A function module populates the CVR (timesheet) parameter dependent on whether you are an employee or a contractor
Occasionally, our HR department request records to be deleted from the SAP Support team - for example if the employee or contractor hasn't in fact joined the company.
Until some time ago, the deletion was causing problems because:
a) the record does not get deleted in AD and there is no way to send the deletion across after
b) when AD tries to reprocess that specific record, LDAP connector will not find it as HR record so what happens in SU01 for some reasons, the VALID from field gets wiped out and the CVR parameter for Timesheet also...
We have changed the process for the deletion however, I would like to ask if you know what is the best practise for this?? HR want to delete the record so it can be re-utilised
I cannot delete those records from UMR unless I am 100% sure they have never used the system (will have to check that)
I hope I have provided enough info on what the issue is..
Thank you
Nadia

Best practice is not to delete.
> HR want to delete the record so it can be re-utilised
So many people with the same name? Perhaps a suffix of 2 numbers when the ID naming convention produces a clash. Besides, do your AD admins not want unique names in the AD as well?
E.g. (just an imperfect example)
MUSTERMA = Alfred MUSTERMan
MUSTERMM = Manfred MUSTERMan
MUSTER01 = Mechtilde MUSTERMuller
> I cannot delete those records from UMR unless I am 100% sure they have never used the system (will have to check that)
Surest way is to determine that they have never logged on before. But that does not exclude that records might exist for them, which may eventually do a "user existence check" to be read. One such example is the Security Audit Log, e.g. there may have been failed login attempts.
Good luck,
Julius

Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade

A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management. Our consultants come with significant global experience implementing projects for the worlds largest corporations.
Archiving before Upgrade
It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
Archiving also yields Long-term Cost Savings
By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.

Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html

Best practise to versioning Web Service WCF

I've a web service SOAP developed with WCF, there is a best practise to versioning it? when I change the contract I don't want to update all the client's referiments but I want simply publish a new version that coexists with the old.
STUDY-CASE: I've a web service with one endpoint, all clients point to it, soon I will have to change the contract and I search a way to avoid that all clients crash. I know two ways to avoid this:
publish the web service with the new contract in another server
create a new file svc with the new contract
there are other ways?

It depends on many things such as what changes you are going to make, what platform your clients are built on, what's your change tracking policy, etc.
For example if you just want to add a new property to a data contract or a new operation to a service contract it's safe to add it to your current implementation as long as the clients are version tolerant (DataContractSerializer is version tolerant) and it
complies with your change tracking policy. However you would better stick to strict versioning strategy which requires creating a new contract and exposing it with a new endpoint in case the changes are more serious.
I suggested reading these articles:
Versioning Strategies
Best Practices: Data Contract Versioning
This should help you to choose the right version strategy and provide your with the best practices to follow.

SAP Best Practises - Installation

Hello All,
I had installed SAP best Practises base line package SAP BP-ERP 617V6 in my system a couple of weeks back. But now when I am trying to activate the Best practises it is asking for the solution scope files and the installation text files. But when I am checking on Service market place , it seems SAP has with drawn the files for 617-V6 and has updated them with the latest files of 617-V7.
Now without these files I cannot proceed any further. And I have already activated the Business sets and Business Enterprise Functions in Client 000 and created a new client from 000.
In this regards can anyone advise what will be the best way forward. Can I upgrade my BP version BP-ERP 617-V7 now and proceed. Are there any special steps that I need to do for the BC sets which are already activated. I am guessing I will need to a client copy once again.
I also went through SAP Note 1301301 , Point IV , which talks about the upgrade of SAP BP package but it lacks clarity on the above points.
I have also raised a Customer message on this but will really appreciate your views in this regards.
Thanks
S

Hello Surajit Das,
In http://service.sap.com/swdc have you tried looking in Archive Area ?
SAP will generally hold the previous versions of software and components in the archive area for some time.
Regards,
Siddhesh

SDO_PC, multiple SRIDs - best practise for data model?

Hi,
im using UTM and I am getting data covering two zones.
all my existing data is from zone A.
tables:
pointcloud
pointcloud_blk
now im getting data with very few points from zone A and most points from zone B. It was agreed that the data delivery will be in SRID for zone B.
so I tested whether this would work. I had two pointclouds. One with SRID A, another with SRID B. As soon as I put SRID B pointcloud inside, I could NO LONGER QUERY pointcloud with SRID A.
So it seems to be necessary to use at least another pointcloud_blk, f.e. pointcloud_blk_[srid].
Question: does another pointcloud_blk for each SRID suffice or do i also need a pointcloud table per SRID. the pointcloud table seems only interesting due to its EXTENT column. But on the other hand this could be queried by "function", since there are only 10 or so records (pointclouds) inside.
PLZ share your best practises. What does work, what not.

It is necessary to have one pointcloud_blk table for each SRID since there is a spatial index on that table.
As for the PointCloud table itself, it is up to you. You can have pointclouds with different SRIDs in that table.
But if you want to create spatial index on it, you have to use some function based index so that the index
sees one SRID for the table.
Since this table usually does not have many rows, this should work fine with one table for different SRIDs.
siva

Record Center Archival Strategy/Best Practise

Similar Messages

Maybe you are looking for