Hi Karel!
From the Admin guide:

Decommission VM command:
"When a virtual machine is no longer needed in your production environment, you 
can issue this command to initiate a staged removal of the virtual machine file 
space from the server. The DECOMMISSION VM command marks all data that was 
backed up for the virtual machine as inactive, so it can be deleted according 
to your data retention policies. After all data that was backed up for the 
virtual machine expires, the file space that represents the virtual machine is 
deleted."

So the file space should be removed by TSM automatically as soon as all data 
has expired...
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Karel 
Bos
Sent: dinsdag 4 oktober 2016 6:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Decommision VM?

Data in filespaces gets expired. Filespaces by itself will not get removed 
automaticly.

Op 3 okt. 2016 19:32 schreef "David Ehresman" <david.ehres...@louisville.edu
>:

> >q copyg it-vme active standard
>
>
>
> Policy    Policy    Mgmt      Copy      Version- Version-  Retain  Retain
>
> Domain    Set Name  Class     Group      s Data   s Data    Extra    Only
>
> Name                Name      Name        Exists  Deleted Versions Version
>
> --------- --------- --------- --------- -------- -------- -------- 
> -------
>
> IT-VME    ACTIVE    STANDARD  STANDARD  No Limit No Limit       30      30
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
> Of Francisco J
> Sent: Monday, October 03, 2016 1:09 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Decommision VM?
>
>
>
> could share the output for:
>
>
>
> query copygroup ??        ??
>
>
>
>
>
> Bests regards
>
>
>
>
>
> 2016-10-03 11:49 GMT-05:00 David Ehresman 
> <david.ehres...@louisville.edu
> <mailto:david.ehres...@louisville.edu>>:
>
>
>
> > I decommissioned a VM on 9/1/2016.  We have a 30 day retention of data.
>
> > The filespace still has not been removed even tho it is now 10/3/2016.
> Why
>
> > not?
>
> >
>
> > Output from a q file shows the filespace is decommissioned.
>
> >
>
> >                                        Platform: TDP VMware
>
> >                                  Filespace Type: API:TSMVM
>
> >                           Is Filespace Unicode?: No
>
> >                                        Capacity: 0 bytes
>
> >                                        Pct Util: 0.0
>
> >                     Last Backup Start Date/Time: 08/30/2016 03:13:32
>
> >                  Days Since Last Backup Started: 34
>
> >                Last Backup Completion Date/Time: 08/30/2016 04:09:46
>
> >                Days Since Last Backup Completed: 34
>
> > Last Full NAS Image Backup Completion Date/Time:
>
> > Days Since Last Full NAS Image Backup Completed:
>
> >         Last Backup Date/Time From Client (UTC): 08/30/2016 08:00:19
>
> >        Last Archive Date/Time From Client (UTC):
>
> >                Last Replication Start Date/Time: 10/03/2016 10:49:29
>
> >             Days Since Last Replication Started: <1
>
> >           Last Replication Completion Date/Time: 10/03/2016 11:08:51
>
> >           Days Since Last Replication Completed: <1
>
> > more...   (<ENTER> to continue, 'C' to cancel)
>
> >
>
> >                    Backup Replication Rule Name: DEFAULT
>
> >                   Backup Replication Rule State: Enabled
>
> >                   Archive Replication Rule Name: DEFAULT
>
> >                  Archive Replication Rule State: Enabled
>
> >          Space Management Replication Rule Name: DEFAULT
>
> >         Space Management Replication Rule State: Enabled
>
> >                                    At-risk type: Default interval
>
> >                                At-risk interval:
>
> >                                  Decommissioned: Yes
>
> >                             Decommissioned Date: 09/01/2016 13:09:12
>
> >                                     MAC Address:
>
> >
>
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************
                        

Reply via email to