8 Krypton

Re: Restoring expired save set information into client index with scanner

Jump to solution

They will not get touched at all.

0 Kudos
8 Krypton

Re: Restoring expired save set information into client index with scanner

Jump to solution

I have multiple media file numbers for each SSID:

/usr/sbin/nsr/mminfo -avot -s bdlbkp -r "ssid,cloneid,mediarec,mediafile,name,totalsize,savetime,volume,state,ssretent,ssbrowse" -q "client=sdbkp"

ssid        clone id  rec file name                                total  date  volume        state  retent  browse

1631254415  1441494519    0  677 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  695 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  678 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  694 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  658 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  679 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  680 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  654 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  681 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  682 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  683 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  684 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  685 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  653 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  652 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  686 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  687 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  688 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  693 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  690 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  691 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  692 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  659 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  657 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  660 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  661 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  662 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  663 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  656 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  664 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  665 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  655 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  666 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  667 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  668 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  669 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  670 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  671 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  672 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  673 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  674 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  675 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  676 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

1631254415  1441494519    0  689 RMAN:/home/scripts/sddb_backup.rcv 362 GB 09/06/15 SD56LT  03/03/16 10/18/15

In such case should I give the lowest as argument of scanner?

scanner -f 652 -r 0 -i -S 1631254415 /dev/rmt/0cbn

0 Kudos
8 Krypton

Re: Restoring expired save set information into client index with scanner

Jump to solution

That's the logic. However, you better forget about the file and record numbers.

You still have the media index which knows exactly where to start.

You can also say that the media index 'maps the logical entity (the save set) to the physical location on tape'.

File and Media Records really make a difference if you run a DR - while your media index is empty. That's when NW will ask you about the physical location to speed up the positioning towards the beginning of the bootstrap save set.

0 Kudos
8 Krypton

Re: Restoring expired save set information into client index with scanner

Jump to solution

If I still have the media index, do I have to load the volume (without mounting) into device before scanning, or could I just mount it?

0 Kudos
8 Krypton

Re: Restoring expired save set information into client index with scanner

Jump to solution

In this is up to you. Both will work. Try it.

However, if it does not have a media index entry you do not have the chance to mount it.

0 Kudos
8 Krypton

Re: Restoring expired save set information into client index with scanner

Jump to solution

I managed to make expired backups browsable with scanner -f <file record number> -r <media record number> -i -S <SSID> /dev/rmt/1cbn. Thanks for helpful comments.

I noticed that after scanning I had to manually extend browse time by nsrmm -S <SSID> -s bdlbkp -w "03/02/2016" - it was not changed by scanner and if I didn't change it some save sets would return to recoverable state.

0 Kudos
8 Krypton

Re: Restoring expired save set information into client index with scanner

Jump to solution

This is correct. Scanner will not adjust these values - there is not option to do this - it will just read what it has found.

So if you want to change the browse/retention dates after the scanner, you must act appropriately.

Do not forget that the time policies apply exclusively at the time the backup has been created.

These relative values will be converted into the absolute time stamp which then is stored in the indexes.

Consequently you can only change the time stamps later. Policies do not apply any longer.

0 Kudos
3dPrinterfan
1 Copper

Re: Restoring expired save set information into client index with scanner

Jump to solution

If I still have the media index, do I have to load the volume (without mounting) into device before Scanning <Non-public info removed> or could I just mount it?

0 Kudos
8 Krypton

Re: Restoring expired save set information into client index with scanner

Jump to solution
- As long as the volume exists in the media index you can either load and mount it. - It it is missing in the media index you only load it - mounting is impossible.
0 Kudos