ldmwndletsm
ADSM.ORG Senior Member
- Joined
- Oct 30, 2019
- Messages
- 232
- Reaction score
- 5
- Points
- 0
I don't think I've ever run into this problem before. We have a client that used to have a /var/tmp file system, so "tmp" was not simply a directory under /var, although I think the /var file system also existed. Now, we no longer have /var/tmp as a separate file system, only /var, but there is a "tmp" directory under /var. I checked, and tmp is not a symbolic link, and there is no entry in /etc/fstab for /var/tmp (even a bind mount), only /var. There are no excludes for /var in dsm.sys.
Problem is how do I restore something under the current /var/tmp subdirectory? I believe TSM is confused and thinks that I'm trying to restore it from the old /var/tmp file space that previously existed, and the file was never backed under there.
I can see in dsmched.log that files under the current /var/tmp are being Sent during backups with no errors -- all good. Also, if I run this: "dsmc q backup /var -subdir=yes | grep tmp", I can see the files listed with the recent backup date, all Active. However, if instead I run this: "q backup /var/tmp/filepathname", it doesn't find it, so it appears that TSM is trying to find it under the old file space /var/tmp, where, of course, it was never backed up. I can run "q filespace", and I see "/var/tmp" listed with an old backup date, and, yes, I can query data under there, but nothing from the more recent backups of /var/tmp wherein tmp is now a subdirectory.
How do we resolve this mess? Sheesh! What a mess.
Actually, I don't need to restore anything under there -- don't know that we'd ever have to or would want to? -- so I'm just asking how you'd get around this type of problem if, say, it was some other scenario not involving some tmp directory where there could be something that might need to be restored.
Problem is how do I restore something under the current /var/tmp subdirectory? I believe TSM is confused and thinks that I'm trying to restore it from the old /var/tmp file space that previously existed, and the file was never backed under there.
I can see in dsmched.log that files under the current /var/tmp are being Sent during backups with no errors -- all good. Also, if I run this: "dsmc q backup /var -subdir=yes | grep tmp", I can see the files listed with the recent backup date, all Active. However, if instead I run this: "q backup /var/tmp/filepathname", it doesn't find it, so it appears that TSM is trying to find it under the old file space /var/tmp, where, of course, it was never backed up. I can run "q filespace", and I see "/var/tmp" listed with an old backup date, and, yes, I can query data under there, but nothing from the more recent backups of /var/tmp wherein tmp is now a subdirectory.
How do we resolve this mess? Sheesh! What a mess.
Actually, I don't need to restore anything under there -- don't know that we'd ever have to or would want to? -- so I'm just asking how you'd get around this type of problem if, say, it was some other scenario not involving some tmp directory where there could be something that might need to be restored.