Thanks for your reply. The browse time was from last week so it shouldn't be because I'm going too far back with a restore date. This is not the first time this happens and find it odd that it requires other media than was used for the full backup.
Perhaps I'm not understanding the full backup process properly. In my head, if it took a full backup of everything last week for example, then I shouldn't need any other tapes than what was used for that full backup, no matter how old the files are, assuming I want to restore something after that full backup was taken.
bingo.1
2.4K Posts
0
May 7th, 2018 09:00
Good question. It could be a bug.
But this is also possible if you use an earlier browse time.
Querying the databases should reveal the details.
Zuka007
1 Rookie
•
33 Posts
0
May 7th, 2018 10:00
Thanks for your reply. The browse time was from last week so it shouldn't be because I'm going too far back with a restore date. This is not the first time this happens and find it odd that it requires other media than was used for the full backup.
Perhaps I'm not understanding the full backup process properly. In my head, if it took a full backup of everything last week for example, then I shouldn't need any other tapes than what was used for that full backup, no matter how old the files are, assuming I want to restore something after that full backup was taken.
bingo.1
2.4K Posts
0
May 8th, 2018 04:00
This may be correct. But where the data finally resides also depends on you pool configurations.
And whether fulls anc incrementals are stored within the same pool.
And it could be that NW wants to reatore from a clone tape if there is a suspect save set.
But of course I agree that the timestamps should be close.