05-25-2012 01:44 AM
Hi,
Restore successfully but the right file is not restored. The restore Log say that i need to reboot the server ..that the file to take effect. Why this error? I can't reboot the server after each restore process.
What is wrong?
Solved! Go to Solution.
05-25-2012 03:58 AM
No, the file is restored - hence why it is a warning.
NBU has done it's job, it is not the fault of NBU that the file is open.
If the file is open, NBU can restore it, but until the file is closed (or system rebooted) it does not become effective.
Thanks,
Martin
05-25-2012 02:12 AM
I suspect this is a file that was restore while the currect file on the system was open ?
Hence the reboot message.
Ensure the file is closed, then re-run the restore.
Martin
05-25-2012 03:44 AM
This is not an error it is a warning.
05-25-2012 03:53 AM
I have try to restore to another folder and worked. Maybe was broken the Folder.
@Revaroo ...Jeah is not a error is a WRN ..but the files are not restored :). And for me this is a ERROR :).
Regards,
Marius
05-25-2012 03:58 AM
No, the file is restored - hence why it is a warning.
NBU has done it's job, it is not the fault of NBU that the file is open.
If the file is open, NBU can restore it, but until the file is closed (or system rebooted) it does not become effective.
Thanks,
Martin
05-25-2012 07:12 AM
As mph999 says, the file is restored ((temp=D:\Rcksicherung\QQX4MGO1.NBU)
Once you reboot and the lock on that file is released, it should be put into place.
05-25-2012 07:23 AM
why you dont try to restore in to a different box maybe something is wrong with that windows file system or at least in to a different drive just to see if there is any issue with the disk.
05-25-2012 07:35 AM
This is totally normal and will be seen whenever you restore an Operating System or a system file.
It is a little like an installation that requires DLL'd to be registered.
In the case of NetBackup it detects that the file is a system file and has to be fully in use for the Operating System to remain stable - so it give it a temporary name.
Next time the system is rebooted it moves it to the correct location overwring the original file so that it is properly registered and an active part of the operating system when that system boots.
Whatever that file is it is active within the system so needs the reboot to restore it correctly.
You can restore it to another location or you could just copy the temp version out somewhere else and rename it.