04-27-2012 01:11 AM
hi,
I have such a question. we have a Netbackup6.5.4 running on linux server.
the client is windows2003.
I restored 2 files for a SQL Server database. but one of the files shows that the last modified time is 1980-1-1 as below
and here below are the source files that are still kept on the disks.....
the filename and file size are the same ., only the modified time stamp .......
I checked our backup logs and no failed alerts on 4/22..and the restore was also succesfful.
is there any possibility that this is a bug or is there anybody who have ever came accross such questions?
btw: this is the quarterly backup verification job and I did it in Q1 for the same client...and everything was fine last time.
and this time I restored about 10 databases and this is the only database we have problem....
Solved! Go to Solution.
04-27-2012 02:16 AM
Is it possible that there was a big time difference between the client and the master server when the file was backed up? If the timestamp on the file was a newer date/time than the date/time on master server when the backup ran, NBU might have been unable to correctly interpret the timestamp.
Your NBU version is quite o-l-d... Chances are also that it's a bug - there have been so many updates and new versions since 6.5.4.
Please schedule upgrade to 7.1 or 7.5 ASAP to benefit from fixes and updates.
Please also bear in mind that 6.x support is fast approaching EOSL: http://www.symantec.com/docs/TECH74757
Upgrade portal: http://www.symantec.com/docs/TECH74584
04-27-2012 02:16 AM
Is it possible that there was a big time difference between the client and the master server when the file was backed up? If the timestamp on the file was a newer date/time than the date/time on master server when the backup ran, NBU might have been unable to correctly interpret the timestamp.
Your NBU version is quite o-l-d... Chances are also that it's a bug - there have been so many updates and new versions since 6.5.4.
Please schedule upgrade to 7.1 or 7.5 ASAP to benefit from fixes and updates.
Please also bear in mind that 6.x support is fast approaching EOSL: http://www.symantec.com/docs/TECH74757
Upgrade portal: http://www.symantec.com/docs/TECH74584
04-27-2012 08:25 PM
the date and time between the client and the NBU master are consistent. the DBA administrator checked their event logs and it is proved that the file was already corrputed on that day before our Netbackup backup started. so that is why the time stamp is wrong.
and our 6.5.4 is indeed quite old but we also have NBU7.0 and 7.1. we have 9 backup domains in total..and the data center which contains this 6.5.4 backup domain is going to decommission at the end of year...so we don't plan to upgrade it..........
thanks very much for your kind reply. Marianne.
04-28-2012 01:25 AM
Hi Ivy,
If you feel that Mariannes excellent post, that allowed you to investigate and find the casue of the problem helped you, would you be kind enough to mark her post as the solution.
Many thanks,
Martin
05-15-2012 10:43 PM
hi, Martin
thanks for your kindly reminding me
I've already mark Mariannes's post as the solution!