ADSM-L

Re: [ADSM-L] rebinding of objects

2017-02-21 15:24:22
Subject: Re: [ADSM-L] rebinding of objects
From: Del Hoobler <hoobler AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 21 Feb 2017 15:22:48 -0500
HI Michael,

Yes, it will rebind them if you are using the same NODENAME.

If you want multiple COPY type backups with different policies,
you will need to use a different NODENAME.


Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/21/2017 
08:05:37 AM:

> From: Michael Prix <mp AT RS6000.DARKTECH DOT ORG>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 02/21/2017 08:06 AM
> Subject: rebinding of objects
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 
> Hello,
> 
> I'm well aware of the rebinding of objects in case of an incremental 
backup.
> Well documented and proven.
> But what I'm not so sure about is the case of rebinding when using 
API-calls,
> especially in this case for Exchange and MS-SQL.
> You have to use the VSSPOLICY statement to place the backups in the 
right
> MGMT-Class, now face this situation:
> Customer wants to perform monthly and yearly backups of its databases, 
done as
> copy-backups thus not breaking the full and incremental daily backups.
> ONE VSSPOLICY states to place the copy-backup into a MONTH-MGMT-class, 
the
> other VSSPOLICY states to place the copy-backup into a YEAR-MGMT-class
> Both policies will be in different tdp*.cfg files and are used during 
the tdp-
> backup by option /configfile.
> 
> Will there be a rebindung of the old copy-backups when the respective 
other
> tdp*.cfg file is used for a backup?
> 
> -- 
> Michael Prix
> 

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