topic Re: SnapVault status is Idle in ONTAP Discussions

SnapVault status is Idle

amit_choudhury01 — Thu, 05 Jun 2025 06:32:40 GMT

Dear All,

Need some help and suggestion on SnapVault.

We have a Windows 2k8 server and we have OSSV version 3.0.1 installed on it. We have a FAS270 where we created a volume for this server. We used SnapVault to backup one of the drives from the the windows server. It went through for the first time and then SnapVault didn't go through post the initial transfer. Below are the output of SnapVault Snap Sched and Status.

Can anyone of you pls guide me if Im missing out something.

SecondaryFiler> snapvault snap sched
create MCCS01 sv_nightly 15@sun-sat@1 preserve=default,warn=0

SecondaryFiler> snapvault status -l
Snapvault secondary is ON.

Source:                 WindowsFS01:F:\
Destination:            SecondaryFiler:/vol/MCCS01/MCCS01
Status:                 Idle
Progress:               -
State:                  Snapvaulted
Lag:                    1488:06:58
Mirror Timestamp:       Tue Jan 10 06:24:15 EST 2012
Base Snapshot:          SecondaryFiler(0084264769)_MCCS01-base.62
Current Transfer Type: -
Current Transfer Error: -
Contents:               Replica
Last Transfer Type:     Initialize
Last Transfer Size:     15550080 KB
Last Transfer Duration: 03:00:02
Last Transfer From:     WindowsFS01:F:\

SecondaryFiler> snapvault status
Snapvault secondary is ON.
Source Destination State Lag Status
WindowsFS01:F:\ SecondaryFiler:/vol/MCCS01/MCCS01 Snapvaulted 1488:07:10 Idle

Re: SnapVault status is Idle

ismopuuronen — Mon, 12 Mar 2012 17:22:06 GMT

Hi,
your schedule in secondary filer might been incorrect.
You should use -x options when creatin schedule, it is used when creating incremental backup schedules.

Example:
sec>snapvault snap sched -x MCCS01 sv_nightly 15@sun-sat@1

Br.
Ismo.

Re: SnapVault status is Idle

amit_choudhury01 — Tue, 13 Mar 2012 04:28:01 GMT

Hi Ismo,

Thanks for your reply.

I used the same command for scheduling "snapvault snap sched -x MCCS01 sv_nightly 15@sun-sat@1" after that I gave the command "snapvault start -S prim_host:dirpath sec_host:/vol/sec_vol/sec_tree" for the initial start of the SnapVault from Primary Windows host to the NetApp filer.

Am I not supposed to do that.

Regards,

Amit

Re: SnapVault status is Idle

ismopuuronen — Tue, 13 Mar 2012 05:42:05 GMT

hi,

Sorry about my incomplete answer.

You were already made the initial transfer before, so there should't be a need for that.

I think, it should work just by editing the secondary snapvault schedule.

-x options means that the secondary will search the snapshot with the same name from

the primary system when the snapshot occur by schedule, compare it to the latest snapshot in secondary,

then transfers the changed blocks and creates the snapshot in sencondary.

without -x option, secondary just creates a snapshot in secondary.

How's your schedule now?

sec>snapvault snap sched

And from where, did you create a snapvault schedule to your primary in the beginning?

Br.

Ismo.

Re: SnapVault status is Idle

amit_choudhury01 — Tue, 13 Mar 2012 08:27:41 GMT

Hi Ismo,

Below is the output for SnapVault Snap Sched:

SecondaryFiler> snapvault snap sched
create MCCS01 sv_nightly 15@sun-sat@1 preserve=default,warn=0

I created the schedule from the secondary NetApp filer.

Pls let me know your findings.

Regards

Amit

Re: SnapVault status is Idle

sahil_anand — Tue, 13 Mar 2012 10:06:23 GMT

Hey Amit,

I believe you have not used option -x while creating snap vault schedule.

Try create schedule like this way :

snapvault snap sched -x MCCS01 sv_weekly 15@sun-sat@1

Thanks,

Sahil

Re: SnapVault status is Idle

amit_choudhury01 — Tue, 13 Mar 2012 11:39:06 GMT

Hey Sahil,

Thanks for your reply. But I did the same way as mentioned by you.

Regards

Amit

Re: SnapVault status is Idle

ismopuuronen — Tue, 13 Mar 2012 16:46:41 GMT

Hi,

Let's try it once more.

The thing is, that output from...

>snapvault snap sched

create MCCS01 sv_nightly 15@sun-sat@1 preserve=default,warn=0

...is incorrect.

should be

xfer MCCS01 sv_nightly 15@sun-sat@1 preserve=default,warn=0

You can try to unsched, and re create it.

secondary>snapvault snap unsched MCCS01 sv_nightly (removes sv_nightly schedule)

secondary>snapvault snap sched MCCS01 (verify, that schedule has disappear)

secondary>snapvault snap sched -x MCCS01 sv_daily 15@sun-sat@1 (recreate the schedule)

secondary>snapvault snap sched MCCS01 (what is output now?)

Were there any notifications on your console during these steps?

Is this your only snapvault relationship, or is there more? And if yes, are those working properly or in same condition as this?

Br.

Ismo.

Re: SnapVault status is Idle

amit_choudhury01 — Wed, 14 Mar 2012 06:51:44 GMT

Hey Ismo,

Thanks for all your inputs. It worked this time.

Reagrds

Amit.

Re: SnapVault status is Idle

GOPACHAI23 — Mon, 08 Oct 2012 12:04:25 GMT

Hello Ismo,

I need help on OSSV the snapvault on this particular volumes qtrees lag are more than 24 hr. how to check what is the issue takes more than schedueld.

pupa1_bkp:/var fas2040-ch:/vol/vol_AIX_OS_OSSV/Qpupa1_var Snapvaulted 89:32:36 Idle

Regards

P.Gopi

Re: SnapVault status is Idle

ismopuuronen — Mon, 08 Oct 2012 12:24:26 GMT

Hi,

Destination> snapvault snap sched
Destination> df -h <destination_volume>

Destination> snapvault status -l

Br.
Ismo.

Re: SnapVault status is Idle

GOPACHAI23 — Mon, 08 Oct 2012 14:40:30 GMT

Hello ISMO,

Thanks for the info and i checked the Transfer error is " could not read from socket", So pls help what needs to be done?

Regards

P.Gopi

Re: SnapVault status is Idle

ismopuuronen — Tue, 09 Oct 2012 05:57:51 GMT

Hi,

Can you make sure, your source disk etc. isn't full?

Check also destination filer messages file (/etc/messages), and try to search it with volume name, it can give you some more information why it fails.

Br.
Ismo.