Re: SQL statement

2016-01-30 Thread Erwann SIMON
Hi Eric,

You're absolutely right, the SQL resultas are just to be used for further 
analysis.
Anyway, when deleting a filespace, we must now that type is ANY by default but 
we generally have to choose a specific type between backup and archive.

-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

- Mail original -
De: "EJ van Loon (ITOPT3) - KLM" 
À: ADSM-L@VM.MARIST.EDU
Envoyé: Vendredi 29 Janvier 2016 16:09:22
Objet: Re: [ADSM-L] SQL statement

Hi Erwann!
As a matter of fact this one requires a little more care. Null can be the 
result of a filespace backup which is interrupted and never restarted (i.e. 
because it has been excluded from the backup) but you will also see null when 
the filespace is only used for archiving. Creating an archive will not set the 
"Last Backup Completion Date/Time" field.
In the first case you can delete the filespace, in the second case you most 
likely don't want to...
Kind regards,
Eric van Loon
AF/KLM Storage Engineering

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann 
SIMON
Sent: donderdag 28 januari 2016 16:46
To: ADSM-L@VM.MARIST.EDU
Subject: Re: SQL statement

Hi Eric,

You maybe should add a condition if backup_end is null

--
Best regards / Cordialement / مع تحياتي
Erwann SIMON

- Mail original -
De: "EJ van Loon (ITOPT3) - KLM" 
À: ADSM-L@VM.MARIST.EDU
Envoyé: Jeudi 28 Janvier 2016 16:20:57
Objet: Re: [ADSM-L] SQL statement

Hi Skylar!
This is exactly what I was looking for. Thank you very much for your help!!!
Kind regards,
Eric van Loon
AF/KLM Storage Engineering

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Skylar 
Thompson
Sent: donderdag 28 januari 2016 15:59
To: ADSM-L@VM.MARIST.EDU
Subject: Re: SQL statement

Hi EJ,

I think this will do the trick:

SELECT -
   f.node_name, -
   f.filespace_name, -
   f.backup_end, -
   CAST(ROUND(o.physical_mb/1024) as int) as "GB Stored" - FROM -
   filespaces f, -
   occupancy o -
WHERE -
   o.node_name=f.node_name -
   AND o.filespace_name=f.filespace_name -
   AND days(f.backup_end)<(days(current_date)-30) - ORDER BY o.physical_mb DESC

On Thu, Jan 28, 2016 at 02:43:54PM +, Loon, EJ van (ITOPT3) - KLM wrote:
> Hi guys!
> I'm trying to join the filespaces and occupancy tables in one SQL statement, 
> but I get stuck on the point where I want to calculate with the amount of 
> days...
> I would like to create a list of filespaces (node_name, 
> filespace_name,backup_end) which are not backed up for more than 30 days, 
> along with the amount of data stored for them in GB 
> (cast(round(physical_mb/1024) as int) as "GB Stored"), sorted on size, the 
> largest first.
> Can anybody help me out here? Thank you very much for your help in advance!
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
> 
> 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
> 

--
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine

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 respons

Re: VM backup question

2016-01-30 Thread Robert Ouzen
Hi Ray

Thanks for this input ..

It is a way to do a general  INCLUDE for "Hard Disk 1"   (ALL VM needs the 
"Hard Disk 1"  to be backup) .

For machines I need to back up more than the "Hard disk 1"  I will add for each 
of them :

INCLUDE.VMDISK VMACHINE1  "Hard Disk 2"
INCLUDE.VMDISK VMACHINE1  "Hard Disk 3"

Best Regards

Robert



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Storer, Raymond
Sent: Thursday, January 28, 2016 3:16 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] VM backup question

Robert, you might use the -vm parameter to exclude certain VMs in your DSM.OPT 
file.
DOMAIN.VMFULL VMHOSTCLUSTER=CLUSTER_NAME;-VM=VM_TO_EXCLUDE1,VM_TO_EXCLUDE2

Also, in your DSM.OPT file you can add INCLUDE.VMDISK options to specifically 
target VM disks you want (which excludes the other disks you do not 
specifically include).
INCLUDE.VMDISK EXACT VM NAME GOES HERE "Hard Disk 1"

Disk(s) not specifically included restore blank at their full size during a 
full VM restore.  I forget if a way exists to prevent the other disks from 
restoring in a full restore.

If you see issues with VM backups or restores, you might also consider adding 
testflag VMBACKUP_UPDATE_UUID to your DSM.OPT file to force the backup to save 
the UUID every time you perform a VM backup.

Good luck!

Ray Storer
NIBCO INC.
574.295.3457

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert 
Ouzen
Sent: Wednesday, January 27, 2016 11:31 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] VM backup question

Hi to all

I have a VMware farm with around 300 VM machines and I try to figure the best  
way to configure the backup with TSM for VE V7.1.4 .


1.   Need to backup for all the machines the "Hard disk 1"

2.   Our structure don't let us to do it with VMfolder , think about 
domain.vmfull vmdatastore= data1.,data2, etc

3.   Need for some VM machines to backup all disks or at least more than 
"Hard disk 1" ,  and some machines not to back up at all

Any help will be appreciated 

Best Regards

Robert



CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive 
and confidential use of the intended recipient. If you are not the intended 
recipient, please do not read, distribute or take action in reliance upon this 
message. If you have received this in error, please notify us immediately by 
return email and promptly delete this message and its attachments from your 
computer system. We do not waive attorney-client or work product privilege by 
the transmission of this message.