Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

Frank02

11 Posts

1712

November 26th, 2008 11:00

symclone BCV create fails after session activated against same STD Devices.

According to the SE manual for 6.5.2, in the section titled "Understanding copy session limits" in Creating a clone copy session section, up to 16 clone "sessions" are allowed. The manual later gives an example using concurrent BCV pairs, but does not go on to state what happens when TWO target groups are employed, for example, moving the STDs between the two to achieve the "independent" point in time copies desired. As a result, we are being forced to "teminate" any prior sessions against the other set of BCV prior to create for any given device group.

Does anyone have an experience to share, or should I open a support case as an "issue". We are currently using SE 6.5.1 on this SYMCLI host.

xe2sdc

2 Intern

 • 

2.8K Posts

November 26th, 2008 15:00

Can you please post output of failing commands ?? I guess you simply need an unintuitive option (see primus emc180840) .. however I need to see what commands you issue and what error you receive .. :D

Message was edited by:
Stefano Del Corno

Frank02

11 Posts

December 3rd, 2008 10:00

Thanks for pointing out the emc solution. By the way, the EMC solution incorrectly states the options file "directory" as /var/symapi/options and should be /var/symapi/config/options in which the mult parameter is set to DISABLE

It seems to mean that the same STD device can be in multiple device groups, but can there be independent clone copy sessions going on at the same time against a different set of BCV in each device group?

xe2sdc

2 Intern

 • 

2.8K Posts

December 3rd, 2008 12:00

The "old" behaviour (pre-6.5) won't allow you to have the same source in two different DGs. The new behaviour (enabled via options file) allows you to put the same STD device in two different DGs .. If you look at the examples in the primus, you'll find that the aim is exactly to allow commands again same STD but via different DGs. Same STD, different DGs, different BCVs/targets :-)

I'll try to notify primus owner regarding incorrect path.

xe2sdc

2 Intern

 • 

2.8K Posts

December 4th, 2008 13:00

Are you saying that I also have to use the
-concurrent operand on the symclone command, in order
to start a second "active" clone copy session with
success ?


Yep... That's why I said you have to use an unintuitive option :-)

If this is done, will I be affecting the first clone
copy session in any way?


Nope.

Regardless, I understand that I will need the -multi
operand on the device group queries to discover all
sessions against any devices in the device group.


Yup.. With -multi you'll ask to show ALL sessions, regardless of the DG you query. You'll find a flag that will show you if the pair is in the DG you queried.

Have fun with SymCli ;-)

Frank02

11 Posts

December 4th, 2008 13:00

Attempted to create a new clone session with a second device group containing the same STD but a different BCV (symclone -g DG2 create -precopy -differential -nop) and received error message "The device is already in the requested state".

Are you saying that I also have to use the -concurrent operand on the symclone command, in order to start a second "active" clone copy session with success ?

If this is done, will I be affecting the first clone copy session in any way?

Regardless, I understand that I will need the -multi operand on the device group queries to discover all sessions against any devices in the device group.

Was this post helpful?

View All

No Events found!

Top