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
exp
I just replied to you prior post, so there is some overlap. But now my
suggestion can be more specific:
dsmc query backup \\wnjcr03p\f$\ -inactive
That will show all active and inactive objects in the root of F:
The point-in-time restore from the GUI requires directory backups that were
crea
I ran a dirsonly selective backup of the F drive: selective f:\ -subdir=yes
-dirsonly
I figured this would allow the PIT restore to have the dirs. it needed.
It backed up:
Total number of objects inspected: 183,714
Total number of objects backed up: 183,714
But, when I now fire up
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
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://www.mail-archive.com/adsm-l@vm.marist.edu/msg07963.html
As an alternative, the comm
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 Wi
