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@avagotech.com] Sent: Saturday, March 31, 2012 02:54 To: Borzenkov, Andrey Cc: toasters@teaparty.net Subject: Re: Operations Manager / Backup Manager.

Andrey,

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 PM.

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.

Thanks,

Jeff

On Thu, Mar 29, 2012 at 10:10 AM, Borzenkov, Andrey andrey.borzenkov@ts.fujitsu.com 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?

https://kb.netapp.com/support/index?page=content&id=1011499 https://kb.netapp.com/support/index?page=content&id=1011262

---

From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley [jeff.cleverley@avagotech.com] Sent: Thursday, March 29, 2012 18:01 To: toasters@teaparty.net Subject: Operations Manager / Backup Manager.

Greetings,

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 relationships.

Does anyone know how to get these relationships into OM without having to do a new baseline?

Thanks,

Jeff

-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611 _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611

Sto,

I think I may have them all functioning at this point in time. It has been ~10 hours since the last time I added them and they are still here. Hopefully they will stay put. Just for the record, here is what appears to have worked. Maybe I'll be able to find it in 4 years when I need it again :-)

1. The physical move of the disk shelves brought the snapvault relationship information with them. A snapvault status showed that without having to do anything after changing ownership of the disks and bringing the aggregates online.

2. I did a snapvault start -S <primary dir> <secondary dir> to update the relationship. This showed on the clients in a snapvault destinations output.

3. I did the dfbm secondary volume add of all the destination volumes.

4. I did the dfbm primary dir add of all the primary qtrees.

5. I ran a snapvault update from the command line which may not have been needed.

6. I did a "Back up now" of each primary directory from the Backup tab. I think this may be what locked everything in and kept them from disappearing.

I still need to do a snapvault release on all the clients to remove the relationship to the prior NearStore. Hopefully this will fix things and we'll be good to go.

Thanks Andrey and Sto for the help and suggestions.

Jeff

On Sat, Mar 31, 2012 at 12:35 AM, Sto Rage© netbacker@gmail.com wrote:

Did you do a "dfbm primary dir relinquish <primary-directories>..." first? That will release these relationships from the OM database. Then you rediscover the relationships on the new NearStore  and finally  use the  dfbm primary dir add  to re-add them back to the datasets as needed.

Also make sure you stop the reaper process first dfm option set dpReaperCleanupMode Never

hope that helps -n

On Thu, Mar 29, 2012 at 7:01 AM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:

...

Greetings,

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 relationships.

Does anyone know how to get these relationships into OM without having to do a new baseline?

Thanks,

Jeff

-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611 _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters