Ok so this is for my notes really… (and for anyone who is interested in having to migrate from SharePoint 2007 based technology!)
So our hosted service provider won’t give us a .spb file (I have no idea why!). In addition to this their advice is to use webdav. Great for copying a single document maybe.. not for performing a migration or archive copy. To make matters worse still we have no central admin access so I can’t use a native backup.
So we rock in with either the following:
- SharePoint Web Services using custom code (c#) – long
- SharePoint Designer 2007 – create a backup to .cmp (nice and easy)
- Buy a third party product to to option 1
In an ideal world our ITSM discipline would be mature enough to not require the use a separate process. A passport document outlining the current service state would already exist in the Configuration Management System, all dependencies would be mapped and would understand support and warranty levels for everything.
Project teams could go to the CMS, the Service Acceptance Criteria (SAC) process would be invoked followed by RFC and Release management ending with a migrated service.
In reality though it is often suggested that a “Passport Process” should be utilised to handle IT transformation activities.
Throttle me this throttle me that…
In-between exam prep I remembered I had started to test the impact of the P2V synchronisation feature. Luckily my lab was in exactly the same state as before I went on holiday therefore to finalise this was going to take me (hopefully) hardly any time.
I logged into converter and selected the last throttled job… previously I had set medium CPU throttling and 15MBps network transfer throttle.