tag:blogger.com,1999:blog-13518440.post6134480455144247185..comments2023-12-12T04:39:52.103-08:00Comments on TSMAdmin: When Data Isn't There, But Is Really There!Chad Smallhttp://www.blogger.com/profile/02637281120881655693noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13518440.post-45452303306117402672010-06-01T09:10:53.113-07:002010-06-01T09:10:53.113-07:00Harry,
Thanks for that I was unaware of the brack...Harry,<br /><br />Thanks for that I was unaware of the bracket option. I'll definitely remember that in the future.Chad Smallhttps://www.blogger.com/profile/02637281120881655693noreply@blogger.comtag:blogger.com,1999:blog-13518440.post-5409101449036455562010-05-31T13:09:17.639-07:002010-05-31T13:09:17.639-07:00Hi,
this may happen - what you can do is to use &...Hi,<br /><br />this may happen - what you can do is to use "{}" brackets around filespace name.<br />So if the file file.txt was originally in the /opt/ mountpoint in directory /ar/ (so the path is /opt/ar/file.txt) and you have another filespace /opt/ar - which does not contain the file - then issue:<br />dsmc restore {/opt}/ar/file.txt<br />What I do when searching such files is the SELECT against BACKUPS/ARCHIVES table(s) to find out FILESPACE_NAME, HL_NAME and LL_NAME<br /><br />HarryHarry_Redlhttps://www.blogger.com/profile/17950374908364822243noreply@blogger.com