Re: [ADSM-L] Trying to delete a filespace???
2011-05-16 05:35:41
Try namet=fsid and use filespace ID instead of name.
FSID can be taken from "q fi <node> f=d".
You will avoid a lot of problems with cpecial characters in filespace name.
Grigori G. Solonovitch
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Minns, Farren - Chichester
Sent: Monday, May 16, 2011 12:10 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Trying to delete a filespace???
Hi all
I'm trying to delete the following filespace and having no luck at all.
The command I'm using is as below and I'm not getting any joy.
Any ideas?
Regards
Farren
delete filespace CHI-AS-SCCMEUR
CHI-AS-SCCMEUR\SystemState\NULL\SystemState\SystemState type=any namet=uni
Node Name: CHI-AS-SCCMEUR
Filespace Name:
CHI-AS-SCCMEUR\SystemState\NULL\System
State\SystemState
Hexadecimal Filespace Name:
4348492d41532d5343434d4555525c53797374656d5-
3746174655c4e554c4c5c53797374656d205374617-
4655c53797374656d5374617465
FSID: 7
Platform: WinNT
Filespace Type: VSS
Is Filespace Unicode?: Yes
Capacity (MB): 0.0
Pct Util: 0.0
Last Backup Start Date/Time: 05/13/11 18:28:59
Days Since Last Backup Started: 3
Last Backup Completion Date/Time: 05/14/11 00:45:55
Days Since Last Backup Completed: 2
Last Full NAS Image Backup Completion Date/Time:
------------------------------------------------------------------------------------------------------------
John Wiley & Sons Limited is a private limited company registered in England
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex,
United Kingdom. PO19 8SQ.
------------------------------------------------------------------------------------------------------------
Please consider the environment before printing this Email.
CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail
message and any attachments hereto may be legally privileged and confidential.
The information is intended only for the recipient(s) named in this message. If
you are not the intended recipient you are notified that any use, disclosure,
copying or distribution is prohibited. If you have received this in error
please contact the sender and delete this message and any attachments from your
computer system. We do not guarantee that this message or any attachment to it
is secure or free from errors, computer viruses or other conditions that may
damage or interfere with data, hardware or software.
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, (continued)
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Dave Canan
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Meadows Andrew
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Zoltan Forray/AC/VCU
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Prather, Wanda
- [ADSM-L] Ang: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Daniel Sparrman
- [ADSM-L] Trying to delete a filespace???, Minns, Farren - Chichester
- [ADSM-L] Ang: Trying to delete a filespace???, Daniel Sparrman
- Re: [ADSM-L] Trying to delete a filespace???,
Grigori Solonovitch <=
- Re: [ADSM-L] Trying to delete a filespace???, Minns, Farren - Chichester
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Paul Zarnowski
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Cheung, Richard
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Loon, EJ van - SPLXO
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Mark Mooney
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Schneider, Jim
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Mark Mooney
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Cheung, Richard
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Mueller, Ken
- Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code, Loon, EJ van - SPLXO
|
|
|