locked
Using Quest Software for Sharepoint migration in SP 2007 RRS feed

  • Question

  • Hi,

    We are looking to migrate sites from a test Sharepoint 2007 farm to another "Live" Sharepoint farm using the software migration tool from Quest. If something went wrong with the migration, would Microsoft still support the Live farm (seeing as how Quest updates the Sharepoint SQL DB directly)?

    Kind regards

    Brett 

    Wednesday, February 23, 2011 3:44 PM

Answers

  • Hi Brett_NZ,

     

    For your case, I would like to make the following suggestions:

    1.       First make a backup of your test and “live” SharePoint farm.

    2.       Then use third-party software to complete the migration.

    3.       If any problem arises and you can’t solve it by yourself, you can restore your SharePoint farm through the backup.

    4.       Since the migration is through third-party software, if any problems occur, I suggest you to contact the vendor for help.

     

    Thanks & Regards,

    Peng Lei

    • Marked as answer by David HM Thursday, March 3, 2011 7:31 AM
    Thursday, February 24, 2011 9:09 AM

All replies

  • i think the Quest is responsible for it? But after the upgrade the Microsoft still support it. As we use tsunami tool for migration and they were responsible during the migration, once they done. I had a few issues with our environment and we open case with MSFT.No issue at all.

     

    Hope this help

    thanks

    -ws


    SharePoint administrator, MCTS,MCITP
    Wednesday, February 23, 2011 4:01 PM
  • Hi Brett_NZ,

     

    For your case, I would like to make the following suggestions:

    1.       First make a backup of your test and “live” SharePoint farm.

    2.       Then use third-party software to complete the migration.

    3.       If any problem arises and you can’t solve it by yourself, you can restore your SharePoint farm through the backup.

    4.       Since the migration is through third-party software, if any problems occur, I suggest you to contact the vendor for help.

     

    Thanks & Regards,

    Peng Lei

    • Marked as answer by David HM Thursday, March 3, 2011 7:31 AM
    Thursday, February 24, 2011 9:09 AM
  • I have used Quest Migration Manager and it is not full fidelity when it comes to metadata.  In my experience, it has flattened our versions (if we had 20 then it flattens them all down to a single version), changed the modified dates on versions, reorders the links in the quick launch menu and some other unflattering affects.  This was while migrating between two 2007 farms. 

    I would definitely recommend making backups and testing migrations a few times to make sure that everything you wish to maintain is done correctly by the tool.

     

    Thursday, February 24, 2011 8:08 PM
  • Thank you all for your comments!

    It sounds generally like the Quest tool should be OK to use then, taking into consideration the comments to make sure we backup everything well, and test what Quest is doing in regards to Flattening versions and modifying dates etc before aplpying to live.

    Thanks for all the advice!

    Kind regards

    Brett

    Friday, February 25, 2011 1:41 PM
  • Hi Brett,

    I'm the product manager for Quest Migration Manager for SharePoint. I stumbled upon your question and wanted to chime in. Migration Manager only use Microsoft-approved ways of writing to SharePoint content databases (no direct SQL writes), so using it will not breach Microsoft's support terms. Having a good backup is always a good idea though :-). You should not have any problems keeping your versions and auditing metadata (Created by/modified by), but I cannot rule out migration issues completely of course. Each real-world SharePoint deployment is unique in many different ways. But you can rest assured that you will get first-class support from Quest should any problems crop up.

    Thanks,

    Alex Kirillov  

    Tuesday, March 1, 2011 11:23 AM
  • Hi,

    Did you contact support about that? This is definitely not how it is supposed to work, so I'd like to look into this if possible.

    Thanks,

    Alex

    Tuesday, March 1, 2011 11:25 AM
  • Hi,

    Did you contact support about that? This is definitely not how it is supposed to work, so I'd like to look into this if possible.

    Thanks,

    Alex


    You didn't quote me, but I am assuming you were directing this comment to me. 

    It's interesting that you say Quest gives first class service if you have any issues with their product; because this is far from the case for my client.

    Yes, I have worked with Quest support on numerous occassions and upgraded each time that support told me that the issue would be resolved in the latest and greatest version of Migration Manager.  However, the issues were never resolved and no hotfixes were ever given when we requested them; we were just told that the behavior was "by design".  I am now experiencing issues with the Quest Recovery Manager, which I have had a few support tickets submitted in the last few weeks.  I upgraded to try to fix the issue that I was having and now the product doesn't work the way the old version did.  In other words, things that were working just fine previously no longer work.  Again, I was told that the issues are "by design" when the previous version of Recovery Manager I was using worked just fine!  Yes, that's going off-topic but speaking from my experience, Quest is not meeting the needs of this corporate customer and not maintaining the same functionality from version to version.  I have requested a hotfix with issues for both tools but all I receive is something along the lines of "we'll make sure your suggestions are considered for our next version". 

    Recently, we purchased the AvePoint DocAve suite of tools and we now do not have the metadata discrepencies that we experienced with Migration Manager.  We don't use AvePoint's recovery or backup tools (because that's what we bought the Quest tools for previously); we just use AvePoint's content and deployment manager utilities.  I had one issue with DocAve so far and they turned around a hotfix to me in less than 2 days to fix the issue.  Now that is customer service!  

    My recommendation to the OP was to make full backups of everything, just in case things don't migrate the way they expected them to.  I have lived to tell about it after using the exact same tools.  Now we may have to look into replacing Recovery Manager, which I wasn't really wanting to recommend to my client since I worked so hard to convince my client to purchase the Quest tools in the first place.

    I didn't want to go so far as to recommend the AvePoint tools in this post as I didn't think it was appropriate.  But, since there is a Quest rep on here defending their product, it's only fair to respond with my real world experience since I'm a user of both AvePoint and Quest products.

     

     

     

    Tuesday, March 1, 2011 3:05 PM
  • You didn't quote me, but I am assuming you were directing this comment to me. 

    It's interesting that you say Quest gives first class service if you have any issues with their product; because this is far from the case for my client.


    I'm really sorry to hear that we were unable to meet your expectations. Could you please help me look into this by letting me know when you contacted Quest support on the behalf of your client?  Please drop me a line (alexander dot kirillov at quest dot com).  

    Regards,

    Alex

    Tuesday, March 1, 2011 5:50 PM