Subscribe

Snapvault for SMVI 3.3 (SV_SMVI) high lag time no updates have been proceeded !

HI, 

 

our customer is using Snapvault with SMVI Version 3.3 since over 200 hours there was no sv update  we can do the snapvault update manually  but if the scheduler tries to do the backup 

 

we recieve the following error [01:01:00] ERROR: Could not find volume for snapshot smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent! 

 

gp-nas03*> snapvault status -l nas01:/vol/GPESX/GPESX1 nas03:/vol/GPESX_sv/GPESX1

Snapvault is ON.

 

Source:                 nas01:/vol/GPESX/GPESX1

Destination:        nas03:/vol/GPESX_sv/GPESX1

Status:                 Idle

Progress:               -

State:                  Snapvaulted

Lag:                    215:43:35

Mirror Timestamp:       Wed May 13 13:01:56 CEST 2015

Base Snapshot:         nas03(1575007764)_GPESX_sv-base.2

Current Transfer Type:  -

Current Transfer Error: -

Contents:               Replica

Last Transfer Type:     Update

Last Transfer Size:     250440 KB

Last Transfer Duration: 00:01:30

Last Transfer From:     nas01:/vol/GPESX/GPESX1

 

 

 

 

gp-nas03*> snapvault status -l nas01:/vol/GPESXL0/GPESX_L0_1 nas03:/vol/GPESXL0_sv/GPESX_L0_1

Snapvault is ON.

 

Source:                 nas01:/vol/GPESXL0/GPESX_L0_1

Destination:            nas03:/vol/GPESXL0_sv/GPESX_L0_1

Status:                 Quiescing

Progress:               -

State:                  Snapvaulted

Lag:                    263:46:15

Mirror Timestamp:       Mon May 11 13:00:50 CEST 2015

Base Snapshot:          nas03(1575007764)_GPESXL0_sv-base.1

Current Transfer Type:  Check

Current Transfer Error: could not read from socket

Contents:               Transitioning

Last Transfer Type:     Update

Last Transfer Size:     23470436 KB

Last Transfer Duration: 00:31:51

Last Transfer From:     nas01:/vol/GPESXL0/GPESX_L0_1

 

 

log output :

LOG REPORT FOR SV-SMVI
-----------------------------------------------------
[01:01:00] SV-SMVI Version: 3.0.3
[01:01:00] Log Filename: C:\NetApp\SV-SMVI\daily_nas01\SV-SMVI_20150521_010100.log
[01:01:00] Start Time: Thu May 21 01:01:00 2015
[01:01:00] Using -svschednames, only taking SnapVault snapshots on specific schedule names ...
[01:01:00] Saving SnapVault schedule name smvi ...
[01:01:00] Use of -svip overrides IP address(es) in SMVI post-backup output. Continuing.
[01:01:00] Found backup: HOST = '10.1.8.60', VOLUME = 'GPESX', SNAPSHOT = 'smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent' ...
[01:01:00] Use of -svip: Changing HOST = '10.1.8.60' to HOST = '10.1.8.60' ...
[01:01:00] Preserving SMVI backup with storage controller 10.1.8.60, volume GPESX, snapshot named smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent ...
[01:01:00] Found backup: HOST = '10.1.8.60', VOLUME = 'vmware', SNAPSHOT = 'smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent' ...
[01:01:00] Use of -svip: Changing HOST = '10.1.8.60' to HOST = '10.1.8.60' ...
[01:01:00] Preserving SMVI backup with storage controller 10.1.8.60, volume vmware, snapshot named smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent ...
[01:01:00] Found backup: HOST = '10.1.8.60', VOLUME = 'GPESXL0', SNAPSHOT = 'smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent' ...
[01:01:00] Use of -svip: Changing HOST = '10.1.8.60' to HOST = '10.1.8.60' ...
[01:01:00] Preserving SMVI backup with storage controller 10.1.8.60, volume GPESXL0, snapshot named smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent ...
[01:01:00] Found backup: HOST = '10.1.8.61', VOLUME = 'gpesx', SNAPSHOT = 'smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent' ...
[01:01:00] Use of -svip: Changing HOST = '10.1.8.61' to HOST = '10.1.8.60' ...
[01:01:00] Preserving SMVI backup with storage controller 10.1.8.60, volume gpesx, snapshot named smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent ...
[01:01:00] Initializing connectivity to storage controller ...
[01:01:00] Attempting to ping storage controller 10.1.8.60 ...
[01:01:00] Ping of storage controller 10.1.8.60 successful.
[01:01:00] Logging into storage controller 10.1.8.60 ...
[01:01:00] Setting username and password for storage controller 10.1.8.60 ...
[01:01:00] Testing login by ONTAP version from storage controller 10.1.8.60 ...
[01:01:00] ONTAP version: NetApp Release 8.2.2P2 7-Mode: Fri Nov 21 16:18:27 PST 2014
[01:01:00] Storage appliance login successful.
[01:01:00] Looking for snapshot smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent on controller 10.1.8.60 ...
[01:01:00] ERROR: Could not find volume for snapshot smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent!
-----------------------------------------------------
Exiting with return code: 32

 

Re: Snapvault for SMVI 3.3 (SV_SMVI) high lag time no updates have been proceeded !

Hi,

 

maybe the problem is causing of that information:

[01:00:57] Found backup: HOST = '10.1.8.61', VOLUME = 'gpesx', SNAPSHOT = 'smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent' ...
[01:00:57] Use of -svip: Changing HOST = '10.1.8.61' to HOST = '10.1.8.60' ...
[01:00:57] Preserving SMVI backup with storage controller 10.1.8.60, volume gpesx, snapshot named smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent ...

 

The Volume gpesx is on the Host 10.1.8.61 (gp-nas02) and maybe the job trys to find the Volume on the Host 10.1.8.60!

 

gp-nas02> snap list gpesx
Volume gpesx
working...

%/used %/total date name
---------- ---------- ------------ --------
4% ( 4%) 1% ( 1%) May 27 01:01 smvi_GP-VC01_Daily_BackupClass_VM2_NAS02_novmsnap_recent (snapvault)
4% ( 0%) 1% ( 0%) May 27 01:00 smvi_GP-VC01_Daily_BackupClass_VM2_NAS01_novmsnap_recent

 

gp-nas01> snap list gpesx

Volume gpesx does not exist or is not online.

 

Could this be the reason?

 

Regards,

Daniel