The most recent backup of any object (file or directory) should always be
kept, as long as that object exists on the file system. That is, the active
backup copy never expires. So even if the directory was last backed up a
year ago, as long as that directory continues to exist, it should not be
expired.
Try using the command-line client to do a query backup of all files and
directories in the root of the file system (file space):
dsmc query backup \\filespacename\ -inactive
where filespacename is the name of the file space containing the backups of
the objects you are looking for.
I assume that F: is mapped to some shared directory name (let's call it
"\\somemachine\share"), and the directory you seek is in the root, so:
dsmc query backup \\somemachine\share\ -inactive
Regards,
Andy
P.S. I just noticed who I was responding to in that older post, that's a
trip down memory lane... :-)
____________________________________________________________________________
Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2019-04-30
13:22:48:
> From: "Rhodes, Richard L." <rrho...@firstenergycorp.com>
> To: ADSM-L@VM.MARIST.EDU
> Date: 2019-04-30 13:25
> Subject: Re: [EXTERNAL] Re: Win BA client GUI shows empty drive for
> PIT restore view
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
>
> Yea, I think this hits our problem exactly!
>
> This server holds Windows shares. It doesn't change much - in the
> past 32 days only 18k files/dirs have changed out of over 2.3m.
>
> Now, a year or so ago we made a big change on all our win server
> backups. Prior to this change, we had a default (and only) mgt
> class policies of 32,2,90,365, so dirs would have been bound to the
> RETONLY 365. A year or so ago we changed to 32,32,32,32. All dirs
> that hadn't changed forever were dropped, and thus not there for
> this GUI PIT restore attempt.
>
> From the select I of the backups table, I searched for the top level
> DIR of the path we wanted, F:/Cr-ENG, and it doesn't exist. I
> believe this is true for all top level dirs. And thus, no PIT GUI
display.
>
>
> A Question: When we changed the policies and all the long held dirs
> were deleted out of TSM, why didn't TSM backup them up as new files
> during the next normal incremental backup? Wouldn't TSM see there
> was no backup of the dir and back it up?
>
> Rick
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of
> Andrew Raibeck
> Sent: Tuesday, April 30, 2019 12:28 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [EXTERNAL] Re: Win BA client GUI shows empty drive for PIT
> restore view
>
> Hi Richard,
>
> Check the management class to which the directories are bound, and see
what
> the RETEXTRA and VEREXISTS settings are.
>
> Off the top of my head, this sounds like a topic covered in an older
post:
>
> https://urldefense.proofpoint.com/v2/url?
>
u=https-3A__www.mail-2Darchive.com_adsm-2Dl-40vm.marist.edu_msg07963.html&d=DwIFAg&c=jf_iaSHvJObTbx-
> siA1ZOg&r=Ij6DLy1l7wDpCbTfcDkLC_KknvhyGdCy_RnAGnhV37I&m=ftbxehM6v9lH0a-
>
SR06YQc9x9jOXVuZcnm48VbbX00Q&s=CWiDnPpW0psDTd-L8_l9udcthHCgTxu6BaoBjBX3KXk&e=
>
> As an alternative, the command line client can be used to do the PIT
> restore.
>
> Best regards,
>
> Andy
>
>
____________________________________________________________________________
>
> Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
>
> "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2019-04-30
> 12:07:38:
>
> > From: "Rhodes, Richard L." <rrho...@firstenergycorp.com>
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 2019-04-30 12:16
> > Subject: Win BA client GUI shows empty drive for PIT restore view
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
> >
> > Hi,
> >
> > TSM server 7.1.5
> > Win Server 2012R2 with BA client 7.1.6.2, then upgraded to 7.1.8.4
> >
> > We're trying to do a Point-In-Time restore of a directory on a Win
> > server F drive. (Just one sub dir, not the whole drive.) The mgt
> > class is 32 32 32 32 - one month PIT restorable.
> >
> > When we bring up the Win BA gui client and just look at the F drive
> > we see the active files.
> > When we switch to active+inactive files, we see all versions of files.
> > When we switch to PIT restore and take the default date/time (right
> > "now") we see files as of last nights backup.
> > But ...
> > When we switch the PIT back to any point prior to last nights backup
> > we see NOTHING on the F drive. No files ... No dirs ... nothing.
> > The GUI shows just an empty F drive. (and the F drive has 2.3m files
on
> it)
> >
> > Ran a SELECT from the BACKUPS table for the node and clearly see all
> > the files (active+inactive).
> > Stopped/started BA client - didn't help.
> > Rebooted server - didn't help.
> > upgraded from 7.1.6.2 to 7.1.8.4 - didn't help.
> >
> > We're going after the restore via the active+inactive view. But we
> > don't understand why PIT restore shows absolutely nothing.
> >
> > Any thought are more than welcome!
> >
> > Rick
> >
> >
> >
> >
> >
>
------------------------------------------------------------------------------
>
> >
> > The information contained in this message is intended only for the
> > personal and confidential use of the recipient(s) named above. If
> > the reader of this message is not the intended recipient or an agent
> > responsible for delivering it to the intended recipient, you are
> > hereby notified that you have received this document in error and
> > that any review, dissemination, distribution, or copying of this
> > message is strictly prohibited. If you have received this
> > communication in error, please notify us immediately, and delete the
> > original message.
> >
>
------------------------------------------------------------------------------
>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If
> the reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are
> hereby notified that you have received this document in error and
> that any review, dissemination, distribution, or copying of this
> message is strictly prohibited. If you have received this
> communication in error, please notify us immediately, and delete the
> original message.
>
