We will move a volume, with snapmirror all snapshots, that contains snapshots with long retention. No new snapshot will be taken on the destination when mirroring is complete. Is there a way to set up a snapshot policy that maintain the retention of the snapshots, i.e. delete the daily snapshots when retention period is outdated? RETENTION COUNT daily 60 weekly 52 monthly 36
... View more
My Oracle DBA's have reported issues using SnapCenter whereby following a restore subsequent backups fail due to an undeletable snapshot owned by "SIS Clone". This also results in no snapshots possible to be created (e.g. manual or scheduled SnapMirror snapshots). I have a case raised but thought I'd post here as well. I've looked through mgwd, ems, and sktrace logs but not spotted anything. From their testing it seems consistent that when they follow the scenario "backup->restore->backup" that they get this problem. SnapCenter Server 4.6 P1 Build 4.6.0.7006 OnTap 9.7P17
... View more
Hi, After upgrade vCenter 7.0 update 3, SnapCenter Plug-in for vSphere did not work in vCenter web client as below. - SCV upgrade 4.5 > 4.6 > 4.7, vSphere web client 6.7 open SnapCenter Plug-in for vSphere no problem - after vCenter 6.7 upgrade to 7.0.3, SnapCenter Plug-in for vSphere click the warning jobs or Edit Storage System Failed or Update Resource Group fail with "VI SDK invoke exception:java.net connectexception:connection timed out" - SCV 4.7 upgrade to 4.7P1 same problem - the backup job should be no problem when review SCV backup job log and the netapp controller snapshot list the SCV backup log naming snapshot Refer SCV 4.8 or 4.9 https://docs.netapp.com/us-en/sc-plugin-vmware-vsphere/scpivs44_download_the_ova_open_virtual_appliance.html, in VMware vCenter 7.0.3 versions and higher, the OVA signed by the Entrust certificate is no longer trusted and require install ceritifcates in vCenter Is SCV 4.7 also require install certificate in VMware vCenter 7.0.3? But SCV 4.7 link did not mention https://docs.netapp.com/us-en/sc-plugin-vmware-vsphere-47/scpivs44_download_the_ova_open_virtual_appliance.html Best regards
... View more
Hello Community, I needed to map some NetApp LUNs to Servers on the DR site of a client as a form of DR test. So I broke replication and made a clone of the Volume in question via GUI. After mounting the LUNs from the replicated volume, I tried resyncing the relationship, but it failed with the error: "Failed to change state back to Data Protection". I then proceeded to create a new relationship from Prod to DR without deleting the Cloned DR Volume (which means the replicated data is still on its volume). But the issue with this, is that it has initiated a new baseline transfer of the Volume. What I intend to do is wait till off-business hours to clone the Production volume and initiate a reverse relationship to that volume (on Production) without updating it and resync once again to DR which will change the RW Volume to DP. Then resync. Please is there anyway to resync the replication with the RW Volume I have in DR that failed with the above error about Data Protection or any there method different from what I intend to do and is a better approach I should have taken to achieve this? Please treat as urgent. I look forward to your responses.
... View more
We are in the process of replacing an existing A200 with an A800. One of the facilities we use extensively on some of our AIX systems is SnapDrive for Unix to manage snapshots. When I try to set the credentials for the new A800, it consistently fails with "0001-136 Admin error: Unable to log on to storage system". I checked and the LIF I am attempting to connect via is configured for both SVM management & Data services. # snapdrive config set root 172.20.8.108 Password for root: Retype password: 0001-136 Admin error: Unable to log on to storage system: 172.20.8.108 Please change user name and/or password for 172.20.8.108, i.e. snapdrive config set root 172.20.8.108 or Please set the management interface for 172.20.8.108 to be used as data interface, i.e. snapdrive config set -mgmtpath <mgmtpath> 172.20.8.108 # snapdrive version snapdrive Version 5.3.2P3 Snapdrive Daemon Version 5.3.2P3 I am able to ping that IP without issue. I am also able to run snapdrive commands successfully against the A200, so that implies that the SDU configuration on the machine in question is correct. Any help getting past this would be very much appreciated. Thanks, Bill
... View more