restore of VM

2014-11-20 Thread Leif Torstensen
Hi

Any one know, if it is possible to restore a vm fra TSM for VE and not restore 
all vmdk's

I am doing a restore on another vcenter, and would like to just restore the VM 
system drive and no data drives, but the command like this won't work

dsmc restore vm "01:-vmdk=Hard Disk 2 " -datacenter=differentdatacenter 
-host=localhost -datastore=lokalstore  -optfile=dsm.opt -asnode=x


but I get


ANS9372E Unable to create the virtual machine to be restored due to an invalid 
host name, datacenter name, or datastore name.


Regards

Leif Torstensen
Athena


Re: restore of VM

2014-11-20 Thread Omar Vargas
Hi Leif,

Can you try setting the -vmname option as a temporary workaround?
Your scenario reminds me of apar IT01943. If I recall correctly,
-vmname (with the same vm name) provided a workaround too.
If they are related, it may be worth an attempt.

using your command as example, add -vmname="01"...

original:
dsmc restore vm "01:-vmdk=Hard Disk 2 " -datacenter=differentdatacenter
-host=localhost -datastore=lokalstore  -optfile=dsm.opt -asnode=x

try this:
dsmc restore vm "01:-vmdk=Hard Disk 2 " -vmname="01"
-datacenter=differentdatacenter -host=localhost -datastore=lokalstore
-optfile=dsm.opt -asnode=x

Regards,
Omar


=
Hi

Any one know, if it is possible to restore a vm fra TSM for VE and not
restore all vmdk's

I am doing a restore on another vcenter, and would like to just restore the
VM system drive and no data drives, but the command like this won't work

dsmc restore vm "01:-vmdk=Hard Disk 2 " -datacenter=differentdatacenter
-host=localhost -datastore=lokalstore  -optfile=dsm.opt -asnode=x


but I get


ANS9372E Unable to create the virtual machine to be restored due to an
invalid host name, datacenter name, or datastore name.


Regards

Leif Torstensen
Athena


SV: [ADSM-L] restore of VM

2014-11-20 Thread Leif Torstensen
Hureka

This seems to work, the restore is started


Med venlig hilsen / Best regards
 
Leif Torstensen
Technician
Telefon +45 70253030 
l...@athena.dk

www.athena.dk




-Oprindelig meddelelse-
Fra: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] På vegne af Omar 
Vargas
Sendt: 20. november 2014 15:28
Til: ADSM-L@VM.MARIST.EDU
Emne: Re: [ADSM-L] restore of VM

Hi Leif,

Can you try setting the -vmname option as a temporary workaround?
Your scenario reminds me of apar IT01943. If I recall correctly, -vmname (with 
the same vm name) provided a workaround too.
If they are related, it may be worth an attempt.

using your command as example, add -vmname="01"...

original:
dsmc restore vm "01:-vmdk=Hard Disk 2 " -datacenter=differentdatacenter 
-host=localhost -datastore=lokalstore  -optfile=dsm.opt -asnode=x

try this:
dsmc restore vm "01:-vmdk=Hard Disk 2 " -vmname="01"
-datacenter=differentdatacenter -host=localhost -datastore=lokalstore 
-optfile=dsm.opt -asnode=x

Regards,
Omar


=
Hi

Any one know, if it is possible to restore a vm fra TSM for VE and not restore 
all vmdk's

I am doing a restore on another vcenter, and would like to just restore the VM 
system drive and no data drives, but the command like this won't work

dsmc restore vm "01:-vmdk=Hard Disk 2 " -datacenter=differentdatacenter 
-host=localhost -datastore=lokalstore  -optfile=dsm.opt -asnode=x


but I get


ANS9372E Unable to create the virtual machine to be restored due to an invalid 
host name, datacenter name, or datastore name.


Regards

Leif Torstensen
Athena


Re: Cristie BMR vs Tivoli Fastback for BMR

2014-11-20 Thread Prather, Wanda
FWIW,
I think the target app for Fastback is for folks who have TSM in the data 
center, but then have remote offices that also need backup.  You put a Fastback 
server & disk in the remote office.  That office then has a fully-functional 
backup that's easy to manage and tapeless.  And for DR, that server replicates 
its stuff up to the TSM server.  Its backups are block level so it's doable 
over WAN.  

W 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan 
Forray
Sent: Wednesday, November 19, 2014 3:19 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Cristie BMR vs Tivoli Fastback for BMR

Wanda,

Thanks for confirming what I suspected.  We briefly looked at Fastback BMR 
thinking we could use it for image-style/BMR backups after someone torqued up a 
Linux server so badly, they had to rebuild from scratch.  Once we saw the "no 
ext4 and the OS has to be ext2" requirements/limitations, we dropped it.

Sounds like it has very little use in a TSM environment.  I guess you could run 
BMR backups parallel with TSM backups, solely for the purpose of BMR, but since 
it doesn't sync with the TSM backups,  not sure how much good it would be other 
than a 2nd or 3rd safety-net..

Anybody out there using FastBack BMR?

On Wed, Nov 19, 2014 at 12:49 PM, Prather, Wanda 
wrote:

> Fastback is also a separate server, which backs up to disk only.
> It uses your regular TSM server to replicate to, but it's really 
> reinventing the wheel if you already have regular TSM clients in place.
> Fastback BMR isn't something you add on to your normal TSM clients.
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
> Of Zoltan Forray
> Sent: Wednesday, November 19, 2014 8:07 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Cristie BMR vs Tivoli Fastback for BMR
>
> We looked into using Tivoli FastBack but were completely surprised 
> when it didn't support ext4 filesystems or filesystems >2TB!  From the 
> "*FastBack Client and BMR Hardware Requirements"*
>
> Linux Client only supports Simple & Simple LVM volumes. File system
> supports: EXT2, EXT3 and Reiser FS
>
> On Tue, Nov 18, 2014 at 4:01 AM, Grigori Solonovitch < 
> grigori.solonovi...@ahliunited.com> wrote:
>
> > Hello Eric,
> > We are using CBMR (without TSM initially) and TBMR now for many 
> > years without any problems. We have restored a few production 
> > servers after real crash including dissimilar configuration.
> > After moving to VMware there is no problem at all. We have just 
> > uploaded TBMR ISO images to all VMware hosts to speed up recovery 
> > (without CD-ROM drive).
> > Support from UK is very good. Licenses and support are not free, but 
> > they have some specially license policy for VMware to reduce cost in 
> > comparison with standalone licenses.
> > In addition, they have presented Recovery Simulator recently. It 
> > allows to simulate recovery in VMware environment (backup testing 
> > without touching real VMs) for most valuable VMs or keep it 
> > scheduled at
> all.
> > I have no experience with FastBack and couldn't compare products.
> > Kindest regards,
> >
> > Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank 
> > Kuwait, www.ahliunited.com.kw
> >
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On 
> > Behalf Of Loon, EJ van (ITOPT3) - KLM
> > Sent: 18 11 2014 11:30 AM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: [ADSM-L] Cristie BMR vs Tivoli Fastback for BMR
> >
> > Fellow TSM-ers,
> > We are looking for a bare machine recovery, primarily for Windows 
> > and Linux servers. There seem to be two main products on the market 
> > when using
> > TSM: Tivoli's own Fastback for Bare Machine Recovery and the third 
> > party product Cristie Bare Machine Recovery which seems to be 
> > tightly integrated into TSM.
> > As far as I can judge from reading documentation, some YouTube 
> > video's and a live demo of the Cristie product the latter seems a 
> > lot easier to use and implement, but I haven't had any hands-on 
> > experience of
> course.
> > Has anyone compared the two products, maybe in a live situation? 
> > What are their pros and cons?
> > Thank you very much for you reply 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 imm