andrey.borzenkov at ts
Mar 30, 2012, 10:01 PM
Post #4 of 6
As a wild guess - Backup Manager is using NDMP to discover relationships. You did enable NDMP on new secondary and configured NDMP credentials in Backup Manager?
From: Jeff Cleverley [jeff.cleverley [at] avagotech]
Sent: Saturday, March 31, 2012 02:54
To: Borzenkov, Andrey
Cc: toasters [at] teaparty
Subject: Re: Operations Manager / Backup Manager.
Unfortunately these are not helping.
We are using Backup Manger in Operations Manager, and not Protection
Manager. We already know that whatever is done in PM won't be seen by
OM or from the CLI. That is one of the reasons we don't want to use
I ran "dfbm primary dir add <destinationfiler>:/sv_vldummy
sourcefiler:/vldummy/test" This will show the volume as a primary for
the destination volume. The entry will disappear about an hour later.
I can still do a manual snapvault update, but the relationships in DFM
go away including the schedules, so no snapshots are getting created
after the transfer.
The dfmcmd.log shows the job to create it running, the gui shows the
job completed, but later the svmon shows it was deleted. It doesn't
say why. There are other entries about backupSources tables but I
can't figure out what it means.
There are a few relationships that still work, but we don't know why
they survive and still show up while most of the others fail.
Any ideas would be appreciated.
On Thu, Mar 29, 2012 at 10:10 AM, Borzenkov, Andrey
<andrey.borzenkov [at] ts> wrote:
> Protection Manager has wizard to import existing SnapVault relationship; did you try it?
> Otherwise these KB articles give example how to re-import existing relationship after source change; may be the same technique works in case of destination change as well?
> From: toasters-bounces [at] teaparty [toasters-bounces [at] teaparty] On Behalf Of Jeff Cleverley [jeff.cleverley [at] avagotech]
> Sent: Thursday, March 29, 2012 18:01
> To: toasters [at] teaparty
> Subject: Operations Manager / Backup Manager.
> We have a 3.8 version of OM/DFM that has been managing backups from
> multiple sites to a NearStore. We just moved the shelves to a
> different NearStore yesterday due to disk count limitations.
> Everything went well except OM will not recognize the new destination
> for the relationships.
> A snapvault status on the secondary shows all the relationships and
> the aggregates and volumes are online. We did a snapvault start -S of
> the relationships, a snapvault update, and also a snapvault release on
> the primaries. The primaries all show the correct relationships.
> OM can see the new destination filer and all the volumes, so it has
> access. It has also figured out the original NearStore volumes and
> relationships are not there because it removed them, and also emptied
> the schedules of any backup relationships.
> We tried a "Add new backup" which seemed to have worked except it did
> an Initialize of the relationship according to the snapmirror log file
> and seems to have done a baseline. We cannot re-baseline all of these
> Does anyone know how to get these relationships into OM without having
> to do a new baseline?
> Jeff Cleverley
> Unix Systems Administrator
> 4380 Ziegler Road
> Fort Collins, Colorado 80525
> Toasters mailing list
> Toasters [at] teaparty
Unix Systems Administrator
4380 Ziegler Road
Fort Collins, Colorado 80525
Toasters mailing list
Toasters [at] teaparty