I was trying to implement the compression=enable command on the CLI for the initialize. I also tried it with the correct entry in the snapmirror.conf but it error's saying volume is offline (because its still restricted and uninitialized)!

Another case of NetApp documentation leaving a few things out I think.

Thanks again,
Rich.

Source: prdfiler:SQL_Logs
Destination: fas250:SQL_Logs_recv
Status: Transferring
Progress: 14848 KB
Compression Ratio: 91.9 : 1
State: Uninitialized
Lag: -
Mirror Timestamp: -
Base Snapshot: -
Current Transfer Type: Initialize

That's the only testing I've done to see if it works, but that compression ratio floats around and the CPU is pegged while base lining that way which would lead me to believe it is working.

I'm using 7.3.2P2 and FAS3140's, using single path and it wont work if the dash is there. In the best practices guide (http://media.netapp.com/documents/tr-3446.pdf) there is no dash either (page 26).

Have you guys worked out if you can use compression on the initialization phase yet? I am struggling on that one.

Thanks,
Rich.

I had wondered the same thing about the multi on the snapmirror.conf file, this is the link to the NetApp documentation for 7.3.2 http://now.netapp.com/NOW/knowledge/docs/ontap/… and you can see even on the example they show with only 2 devices they set it up with multi as well (and without the connection name I get an error stating async SM is only allowed when specifying a connection name, ignoring compression option).

The documentation has the dash after the compression though in my lab I just removed it and it worked (I'm not positive but I think at a customer site we had an issue where it wouldn't work on their system *until* they added the dash though).

I was trying to implement the compression=enable command on the CLI for the initialize. I also tried it with the correct entry in the snapmirror.conf but it error's saying volume is offline (because its still restricted and uninitialized)!

Another case of NetApp documentation leaving a few things out I think.

Thanks again,
Rich.

Source: prdfiler:SQL_Logs
Destination: fas250:SQL_Logs_recv
Status: Transferring
Progress: 14848 KB
Compression Ratio: 91.9 : 1
State: Uninitialized
Lag: -
Mirror Timestamp: -
Base Snapshot: -
Current Transfer Type: Initialize

That's the only testing I've done to see if it works, but that compression ratio floats around and the CPU is pegged while base lining that way which would lead me to believe it is working.

I'm using 7.3.2P2 and FAS3140's, using single path and it wont work if the dash is there. In the best practices guide (http://media.netapp.com/documents/tr-3446.pdf) there is no dash either (page 26).

Have you guys worked out if you can use compression on the initialization phase yet? I am struggling on that one.

Thanks,
Rich.

I had wondered the same thing about the multi on the snapmirror.conf file, this is the link to the NetApp documentation for 7.3.2 http://now.netapp.com/NOW/knowledge/docs/ontap/… and you can see even on the example they show with only 2 devices they set it up with multi as well (and without the connection name I get an error stating async SM is only allowed when specifying a connection name, ignoring compression option).

The documentation has the dash after the compression though in my lab I just removed it and it worked (I'm not positive but I think at a customer site we had an issue where it wouldn't work on their system *until* they added the dash though).

good article. Are you sure about the dash after the compression=enable line in the snapmirror? I get this error when I include the dash ” /etc/snapmirror.conf: line 8 Invalid Day of Month Specification, ignoring line” and it seems to work when I take it out.

Also, is it normal to get these errors: “[snapmirror.dst.multipath.connErr:error]: SnapMirror is unable to setup a multipath connection to mir_v_citrixdata, resorting to the standard single TCP connection.” The snapmiror compression needs a connection of type multi-path but there's only one path declared so I think this error is normal.

What do you think?

Thanks
Tony Lamont