February 10, 2022 at 6:25 pm
We are having issue for backup restore from lower version 2012 to 2016. We copied the backup file over the network from other VM and did check the backup file using restore verify and this verify getting fail. Please help with your valuable suggestion.
February 10, 2022 at 6:35 pm
The backup file is more than likely goosed.
Can you post the message it failed with like operating system error 13 or something , will be in the 2016 error log.
Rule out any issues at the source database side and run a DBCC CHECKDB against the source.
Backup to a different drive than you normally do and backup with checksum to add an extra check.
February 11, 2022 at 7:22 am
the Backup file validation failing with Msg 3203 read on .bak failed :13 ( the data is invalid) Msg 3013 Verify Database is terminating abnormally. Tried with all the possibilities with back up with checksum. no luck for me , though other DB backup files were good and only this back up file had an issue ( the size of the db is 212 GB). Please help on this to trouble shoot the issue.
February 11, 2022 at 8:15 am
Does the service account of the target server ( 2016 ) have read authority for the backup file ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 11, 2022 at 9:59 am
Yes. the service account had read permissions on target ( 2016) backup file.
February 11, 2022 at 11:48 am
This was removed by the editor as SPAM
February 11, 2022 at 3:32 pm
Just curious... not including the path of the file, what is the name and extension of the file? The reason I ask is it sounds like they didn't send you a backup file. It sounds like they sent you something else and the name and especially the extension might be a clue there.
Either that or, like Ant-Green suggested above, the file is goosed and you're going to have to try creating it again.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 18, 2022 at 6:15 am
This was removed by the editor as SPAM
April 18, 2022 at 11:45 am
This was removed by the editor as SPAM
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply