Synchronous between 2 site collections to make a backup data

There was many ways to create a backup for your site collection from content-database. For the others purpose, you will find out the best solutions for you situation, and in this sort topic, I will show you how to create a backup content of site collection in disaster case or crashing data.

Content Deployment Path is a part of tool using in SharePoint Server 2010 to sync data from source site collection to destination collection. Source and destination site don't need to be in the same farm server, they may work on other farm but between 2 farms must have a connection. That means you have to have an account can access to destination site collection.

There are a lot of jobs created and sometime it make your system to be slow down or not responding, however it actually only happens for the very first time running.

One more thing need to be warned, that is, if you are performing on crossing server farm, you should take a time to manage security between the farms because SharePoint requires transfering data by secure socket network, if so, you must go to the Central Administration to reconfig Content Deployment Settings to do:
- Enable listening between the sever farms by setting Accept incoming content deployment jobs
- Select Do not require encryption option if you didn't work on SSL administration

After create an Content Deployment Path, you will see the item in the list, and create a job to perform action.

Conclusion: you can monitor the deployment jobs in Central Administration section, and manage all jobs in the setting page. Note: please don't set the schedule too short to avoid the conflict data between 2 jobs in the same path.

Series solutions on document management for officer - Part 3

At the previous posted, I recommended 2 solutions for officer employees. SharePoint 2010 OOTB has not supported enough components to work on documents especially about document management and collaboration. Security is also an important thing and could not separate from content management actions. If there are many actions on the same document at the same time, it would be conflicted when user perform saving execution. Collaboration is the best solutions to solve this problem and for now Microsoft had released a lot of components for collaboration such as Office Web, SharePoint Online (Office 365),... However, another scenarios often has been used frequently in office that is to share some documents (items) in the same department or another departments.

This topic will reduce (save ) your time when you work on document/content management. I produce this component to help you share (items) your documents, it allows:
- Share item(s) to one or many people with specific permission, the permission list is taken from SharePoint permission level.
- Privately item(s) from another users, except for System Account and Site Collection Admin.
- Inherit from parent.

Limitation for free this component:
- Cannot share item(s) for many people with many permissions. For example, if you need to add some people /groups with FullControl and Contributor for this item.
- Cannot get the permission editing for item which are the same permission items.
- Only support SharePoint 2010

Download here