You should be running regular scheduled FULL DB backups of ALL DBs (this includes LS source DB's) and DIFF DB backups too if needed because you need ALL DBs protected...

The issue is IF you have a DB with multiple data files and all of the data files do not need to be the same size (which is usually the...

We do the same except EXCEPT:

Run a full backup on the old server and run a full restore with norecovery on the new server.

Then run your normal nightly...

Did you enable the "Allow inprocess" option in the IBMDA400 Providers for Linked Services?

Run SSMS as Administrator on the new server then connect to SSAS to set the security/options to match the old server.

Backup/Restore the cubes. Re-IP then Re-name the servers...

After the server renames don't forget to change the SQL local server name too:

SELECT @@SERVERNAME

EXEC master.dbo.sp_dropserver 'OldServerName'

EXEC master.dbo.sp_addserver 'NewServerName', @local = 'local'

Restart SQL/Service

I have fixed this several times due to IBM I Client Software installs adding a bogus line in the .net machine.config file:

SSMS will receive the following error when trying to...

If you have the disk space or the DB is not that large the easiest way is to backup the DB to a shared folder using a static named backup...

No notification; however, I like this site: http://sqlserverbuilds.blogspot.com/

The problem is when CV has issues and it will have issues at some point usually on a weekend or Holiday - for example the MediaAgent is down or tape...

Yes.

Install SSAS on the new server (use the same version and fix level as the old SSAS), set the AS security to match the old server, set the...

Run Windows Resource monitor on the server where the DB is being restored and look at the Disk stats.

Also I wanted to say WELCOME André do Nascimento!!

We apply a SP and CU (or MS Security Fix) at the same time then fail over and have not had any issues...

Brandie beat me to it! Use the passive node as a clustered Backup drive and or clustered MSDTC.