Uppgrade to 7.0 + moved to new SAN

[kbergros]

Hi...

We upgraded from veeam backup and replication 6,5 to 7.
It wen't quite well some minor issues.

We have also started to move our virtual machines from or old vmhosts and SAN to our new VM environment (hosts and SAN).

One thing I see is that the backup jobs on the VMs that have been moved to our new environment, takes longer time and is much bigger than on the old environment. But this is the first time I do the job against the new environment, the next backup job is as before when it comes to time to complete and size.
Is this normal when you move to another SAN?

//Kenneth

[dellock6]

Depends if you also cahnged vCenter or not. did you used storage vmotion to move the VMs? In this case if Veeam is connected to the same vCenter, the ID of the Vm should not change and then the backup job should continue.
Unless you are using other dynamic containers as a source for backups, first thing comes to my mind is datastore: if you select datastore for jobs, and you move a VM into another datastore, likely the VM is now managed by another job (related to the new datastore) and so the first backup in the new position is going to be a full.

[kbergros]

Hi...

Thanks for the reply...

We used the same Vcenter when we migrated to new datastores and hosts.

But it is not à full backup, it usually some hundred of MB but the first time after we moved it was around 10 GB, and the machine is 60GB....

Is it safe to continue running the backupps or could it mess something up?

[dellock6]

Uhm, maybe there has been some changes between the two setups (block size of VMFS?) but nothing really comes to my mind.
If the backup is successful you should be good, but the best way to check that everything is ok is as always a surebackup job, in this way you can be sure the VM is recoverable.

[kbergros]

Ok...thanks...

I have tried to restore files and that works...

Will test surebackups..