If you have all of your SQL databases backed up and all of your configuration settings documented, the restore process would be (on the high level):
1. Create a new SharePoint farm with a new config database
2. Re-create configuration settings, web apps, service apps, etc.
3. Re-deploy any additional front-end, index and search, application servers as necessary. Run PSCONFIG to add these to the new farm
4. Re-deploy any customization solutions you had
5. Attach your content databases from backup to the new farm

Lots of manual work. For a smaller farm, SharePoint built-in backup and restore allows to save some time and efforts and protects more configuration that SQL backups. For larger farms consider 3rd party tools and/or scripted farm deployment.

Some additional information can be found here http://technet.microsoft.com/en-us/library/cc261687.aspx (and following the links from this article).

Hope this helps!

It is somewhat a disappointment for me that nothing has really changed in SharePoint 2010 and you still have to jump thru the hoops to restore a SharePoint farm, even when you have a proper farm backup. I guess Microsoft sees that as a low priority for SharePoint team, leaving the space to DPM and partners.

Do you mean you want to move all SharePoint databases to a new SQL Server? There is a procedure for this published at http://technet.microsoft.com/en-us/library/cc512723.aspx.

Hope this helps.

Thanks,
Ilia

I can successfully move the content and AdminContent DB’s.

Everything seems to be ok with SharePoint_Config?

Thanks