ADSM-L

Re: [ADSM-L] freezing a final backup of a vm

2017-05-05 10:21:53
Subject: Re: [ADSM-L] freezing a final backup of a vm
From: Chavdar Cholev <chavdar.cholev AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 5 May 2017 17:20:21 +0300
Hi,
what about if you export vm as .ova and archive it?

On Friday, May 5, 2017, PAC Brion Arnaud <Arnaud.Brion AT panalpina DOT com> 
wrote:

> Hi,
>
> Not sure either if this apar  has been solved, but the web page give a
> solution to the problem : "Rename the filespace back to its original name
> to regain access to this data from the client.". Thus in the case of a
> restore request, you would just have to rename the current filespace name
> to xxx_current and rename the freezed one to the current one ... Has to be
> tested though !
>
> Two other means I could think of : rename the VM in ESX, and do a backup
> with the new name, then name it back to original name.
>
> Or, a much more complicated approach : make use of another target node
> name, same style than this : http://www-01.ibm.com/support/
> docview.wss?uid=swg21688752
>
> Cheers.
>
> Arnaud
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU 
> <javascript:;>]
> On Behalf Of Marco Batazzi
> Sent: Friday, May 05, 2017 2:20 PM
> To: ADSM-L AT VM.MARIST DOT EDU <javascript:;>
> Subject: R: freezing a final backup of a vm
>
> Hello,
> Maybe is not still the case but renaming vm filespace is  not fully
> supported:
> http://www-01.ibm.com/support/docview.wss?uid=swg1IC92869
>
> Open a support ticked to be sure.
>
> Regards
>
> MB
>
>
> -----Messaggio originale-----
> Da: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU 
> <javascript:;>]
> Per conto di PAC Brion Arnaud
> Inviato: venerdì 5 maggio 2017 13:57
> A: ADSM-L AT VM.MARIST DOT EDU <javascript:;>
> Oggetto: Re: [ADSM-L] freezing a final backup of a vm
>
> Hi Gary,
>
> In this case you might make use of "rename filespace" command : just
> rename the filespace corresponding to your VM, and start a fresh backup.
> Doing so will allow to keep your old VM  backup data freezed.
>
> Cheers.
>
> Arnaud
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU 
> <javascript:;>]
> On Behalf Of Lee, Gary
> Sent: Friday, May 05, 2017 1:27 PM
> To: ADSM-L AT VM.MARIST DOT EDU <javascript:;>
> Subject: Re: freezing a final backup of a vm
>
> To Mark:
>
> Thanks for the link.
> However, I must not have made myself clear.
> We need something more akin to the backupset.
> Freeze a backup while allowing further backups to take place afterward.
> Are these allowed on an individual vm?
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU 
> <javascript:;>]
> On Behalf Of Mark Beta
> Sent: Friday, May 05, 2017 7:12 AM
> To: ADSM-L AT VM.MARIST DOT EDU <javascript:;>
> Subject: Re: [ADSM-L] freezing a final backup of a vm
>
> Hello Gary,
> take a look @ http://www-01.ibm.com/support/docview.wss?uid=swg21659826.
> If you have tdp for ve 7.1 or upper, the vm last backup will stay until
> "expire vm" command will be executed.
>
> Regards.
>
> On Thu, May 4, 2017 at 1:57 PM, Lee, Gary <glee AT bsu DOT edu <javascript:;>>
> wrote:
>
> > I have a request to freeze a backup of a vm using tsm for ve for one
> > year after its decommissioning.
> > What happens here is that the vm is turned off, and converted into a
> > template.
> > If I do nothing, will its backups be retained as active, even though I
> > don't back up templates?
> > If not, how to fulfill this request?
> > Tsm server 7.1.7.1.
> >
>

<Prev in Thread] Current Thread [Next in Thread>