Re: Azure support for cloud-based storage pools?

[Del Hoobler]

Hi Steve,

You are correct that it isn't currently supported. It is on the futures 
list, yes. 

If you are interested in this integration and plan to start sending backup 
data to Azure BLOB storage, please join the Spectrum Protect EAP/beta 
program. We would like to have some deeper level discussions with you 
around the requirements.


Del



"ADSM: Dist Stor Manager"  wrote on 10/04/2016 
12:35:22 PM:

> From: "Stackwick, Stephen" 
> To: ADSM-L@VM.MARIST.EDU
> Date: 10/04/2016 12:37 PM
> Subject: Azure support for cloud-based storage pools?
> Sent by: "ADSM: Dist Stor Manager" 
> 
> Didn't make it to EDGE this year, wondering if there is any word on 
> this. According to the DEFINE STGPOOL doc I'm reading, Azure doesn't
> seem to be currently supported for cloud-based pools. Is this on the
> futures list?
> 
> Thanks!
> 
> Steve
> 
> STEPHEN STACKWICK CISSP | Senior Technical Specialist | 301.518.6352
> (m) | stephen.stackw...@icfi.com | icfi.com<
> http://www.icfi.com/>
> ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md 
> 21046 | 443-573-0524, 443-718-4900 (o)
> 

Re: server script to find what schedules a node is associated with?

[David Ehresman]

DEFINE SCRIPT  Q_SCHED DESC="List all backup schedules associated with a node"
UPDATE SCRIPT  Q_SCHED "select domain_name,schedule_name,node_name from
associations - "
UPDATE SCRIPT  Q_SCHED " where node_name like upper('$1%') "

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dury, 
John C.
Sent: Tuesday, October 04, 2016 3:47 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] server script to find what schedules a node is associated 
with?

Anyone have any idea how to query a TSM server (v6 or v7) to find what backup 
schedules a node is associated with? I'm trying to do the reverse of a "q 
assoc" command and looking for  way to supply a node parameter to a script and 
have the TSM server tell me it is in the following list of schedules.
.

Re: server script to find what schedules a node is associated with?

[J. Pohlmann]

Try q sch * * no=

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Dury, John C.
Sent: Tuesday, October 04, 2016 12:47
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] server script to find what schedules a node is associated
with?

Anyone have any idea how to query a TSM server (v6 or v7) to find what
backup schedules a node is associated with? I'm trying to do the reverse of
a "q assoc" command and looking for  way to supply a node parameter to a
script and have the TSM server tell me it is in the following list of
schedules.
.

server script to find what schedules a node is associated with?

[Dury, John C.]

Anyone have any idea how to query a TSM server (v6 or v7) to find what backup 
schedules a node is associated with? I'm trying to do the reverse of a "q 
assoc" command and looking for  way to supply a node parameter to a script and 
have the TSM server tell me it is in the following list of schedules.
.

Azure support for cloud-based storage pools?

[Stackwick, Stephen]

Didn't make it to EDGE this year, wondering if there is any word on this. 
According to the DEFINE STGPOOL doc I'm reading, Azure doesn't seem to be 
currently supported for cloud-based pools. Is this on the futures list?

Thanks!

Steve

STEPHEN STACKWICK CISSP | Senior Technical Specialist | 301.518.6352 (m) | 
stephen.stackw...@icfi.com | 
icfi.com
ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md 21046 | 
443-573-0524, 443-718-4900 (o)

Re: Versions

[Schneider, Jim]

I'm running TSM server 6.3.3.0, TSM for VE 7.1.0.1.

Jim Schneider

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert 
Ouzen
Sent: Tuesday, October 4, 2016 10:05 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Versions

Hello all

A quick question , if my TSM server version is 7.1.6.0  can it possible to 
upgrade my TSM for VE to 7.1.6.2 ???

Or I need before to upgrade my TSM Server version to 7.1.7.0 before ?

T.I.A Regards

Robert

**
Information contained in this e-mail message and in any attachments thereto is 
confidential. If you are not the intended recipient, please destroy this 
message, delete any copies held on your systems, notify the sender immediately, 
and refrain from using or disclosing all or any part of its content to any 
other person.

Versions

[Robert Ouzen]

Hello all

A quick question , if my TSM server version is 7.1.6.0  can it possible to 
upgrade my TSM for VE to 7.1.6.2 ???

Or I need before to upgrade my TSM Server version to 7.1.7.0 before ?

T.I.A Regards

Robert

Re: Decommision VM?

[Hans Christian Riksheim]

A possible caveat may be using DIRMC. Usually it is set up with a lot
longer retention than file data. My decommissioned nodes hang in there with
a few MB of directory information while the file data has expired. I have
no problem with that.

Hans Chr.

On Tue, Oct 4, 2016 at 10:25 AM, Loon, Eric van (ITOPT3) - KLM <
eric-van.l...@klm.com> wrote:

> 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
> >
> >
> >
> > PolicyPolicyMgmt  Copy  Version- Version-  Retain  Retain
> >
> > DomainSet Name  Class Group  s Data   s DataExtraOnly
> >
> > NameName  NameExists  Deleted Versions
> Version
> >
> > - - - -   
> > ---
> >
> > IT-VMEACTIVESTANDARD  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
> >  > >:
> >
> >
> >
> > > 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...   ( 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 

AW: Decommission VM?

[Michael Malitz]

Hi David

If you decommission a vm or node, the active version is changed to inactive and 
the other policy def which you have  -
e.g. verdel= nolimit -   are still recognized. 

May be you still have other inactive fullvm versions of your VM somehow 
connected to your filespace. In any case, If all inactive versions are gone, 
also the VM filespace should be deleted automatically.

test with:   q  vm-ina

Normally, the follwoing is not a good idea  in a production environement, but 
in a test environement you could also do a test with copygroup  retextra and 
retonly values of 0  and then do an expire inventory 




rgds Michael 

-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von David 
Ehresman
Gesendet: Montag, 3. Oktober 2016 19:30
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: Decommision VM?

>q copyg it-vme active standard



PolicyPolicyMgmt  Copy  Version- Version-  Retain  Retain

DomainSet Name  Class Group  s Data   s DataExtraOnly

NameName  NameExists  Deleted Versions Version

- - - -    ---

IT-VMEACTIVESTANDARD  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 
>:



> 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...   ( 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:

>

Re: Decommision VM?

[Loon, Eric van (ITOPT3) - KLM]

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" :

> >q copyg it-vme active standard
>
>
>
> PolicyPolicyMgmt  Copy  Version- Version-  Retain  Retain
>
> DomainSet Name  Class Group  s Data   s DataExtraOnly
>
> NameName  NameExists  Deleted Versions Version
>
> - - - -    
> ---
>
> IT-VMEACTIVESTANDARD  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 
>  >:
>
>
>
> > 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...   ( 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)