ADSM-L

Re: [ADSM-L] dsmc retrieve syntax for a remote node?

2018-04-12 20:14:08
Subject: Re: [ADSM-L] dsmc retrieve syntax for a remote node?
From: Marc Lanteigne <marclanteigne AT CA.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 13 Apr 2018 00:09:06 +0000
Hello,

The other thing to do is put the filespace in squiggly brackets.

dsmc ret {\\machine\x$}\* -fromnode=...

Like Steven, I prefer -virtualnode instead of from node.

With -fromnode, you have to grant the access properly, which is sometimes a
pain.  With -virtualnode, you just need to know the node password or have a
TSM admin ID that has authority on that node, but don't have to worry about
granting access.

-
Thanks,
Marc...
________________________________________________________
Marc Lanteigne
Accelerated Value Specialist for Spectrum Protect
416.478.0233 | marclanteigne AT ca.ibm DOT com
Office Hours:  Monday to Friday, 7:00 to 16:00 Eastern

Follow me on: Twitter, developerWorks, LinkedIn


-----Original Message-----
From: Harris, Steven [mailto:steven.harris AT BTFINANCIALGROUP DOT COM]
Sent: Thursday, April 12, 2018 08:15 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] dsmc retrieve syntax for a remote node?

Hi Jim

\\thatnode\c$\*.*

Retrieves only files in the C$ root directory with a period in the name.

If you want everything under c$ I'd use

ret \\thatnode\c$\*  -fromnode=thatnode -subdir=y

you will also have to specify a destination  as without it will try to put
the data back into \\thatnode

I find it interesting that you use -fromnode.  I had sort of forgotten it
exists.  I normally use -virtualn and if necessary change the node
password.

Cheers

Steve

Steven Harris
TSM Admin/Consultant
Canberra Australia

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Davis, Jim J - (jjdavis)
Sent: Friday, 13 April 2018 8:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] dsmc retrieve syntax for a remote node?

I'm trying to retrieve some old archived data with dsmc from thatnode to
thisnode, and I seem to have forgotten the strange magic involved in
correctly specifying the paths.  So on thisnode,

dsmc> q filespace -fromnode=thatnode

shows me things like

\\thatnode\c$
\\thatnode\e$
\\thatnode\f$

but something like

dsmc> ret \\thatnode\c$\*.* -fromnode=thatnode

and various permutations just returns a message about nothing being
archived by that path name.  What am I missing?

This message and any attachment is confidential and may be privileged or
otherwise protected from disclosure. You should immediately delete the
message if you are not the intended recipient. If you have received this
email by mistake please delete it from your system; you should not copy the
message or disclose its content to anyone.

This electronic communication may contain general financial product advice
but should not be relied upon or construed as a recommendation of any
financial product. The information has been prepared without taking into
account your objectives, financial situation or needs. You should consider
the Product Disclosure Statement relating to the financial product and
consult your financial adviser before making a decision about whether to
acquire, hold or dispose of a financial product.

For further details on the financial product please go to
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bt.com.au&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4&m=3-pj09qI-gTDB0uYeXmPy1xTRbPa5FHari6x5Ah-w5I&s=5IkKuug01MVkhi240axGskmZOX2G40RsjhO-zqBX1JU&e=


Past performance is not a reliable indicator of future performance.

<Prev in Thread] Current Thread [Next in Thread>

ADSM.ORG Privacy and Data Security by KimLaw, PLLC