02-10-2015 09:50 AM
Hi,
I am in the process of swapping out an old fileserver with a new one. The old server is almost full, its out of warranty so its about time I did something.
The old server is running Windows 2003 Server on a HP DL360 G2 ( or something close). Filestorage is on a HP EVA SAN.
The new server is running Windows 2012 R2 on a Hyper V 2012 R2 node. The storage is on a HP 3PAR.
Since I had the time I thought I could take a FULL backup of the Fileshare on the old server and restore the FULL backup to the new server, recreate shares on the new server and be a happy admin.
The backup completed successfully on the old server but after the restoring this backup to the new server (using redirect to the new server) I notice that 240 files were skipped
The disk on the new server was blank and no users have access to it. Why and how can the file already exist on disk when I restore this backup set?
The backup server is running Backup Exec 2014 SP2 and the backup set was stored to a Deduplication storage.
My faith in backup Exec is already poor and things like this does not really improve it.
Solved! Go to Solution.
03-16-2015 11:25 AM
I gave up on BackupExec as a solution and threw it out. For what it counts, thats a least solves my problem.
02-10-2015 04:57 PM
In your backup, did you select the actual disk location and the share? If so, then the file in the share is backed up twice. Hence you have two copies of this file in your backup and during the restore one would be restored before the other.
You should just select the actual disk location and don't select the share.
02-12-2015 12:28 AM
I have selected the phyiscal folder on disk, and not the share.
02-12-2015 12:52 AM
Have you checked if these "skipped" files are already present on the new server or not ?
If they are, run CatTools to check if these files were backed up earlier or not - http://www.symantec.com/business/support/index?page=content&id=TECH222803
02-12-2015 12:54 AM
03-16-2015 11:25 AM
I gave up on BackupExec as a solution and threw it out. For what it counts, thats a least solves my problem.