VTL Cloud Replication Settings error 10054

StarWind VTL, VTL Free, VTL Appliance

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
koconnor
Posts: 3
Joined: Thu Nov 28, 2019 12:09 am

Wed Apr 15, 2020 10:21 pm

Hello,

I am using StarWind Virtual Storage Appliance v8.0.0 (Build 13170, [SwVSA], Win64). I have a FREE license.
I was successful in creating a Virtual Tape Library and multiple Tapes using StarWindX PowerShell scripts.

However, when I go to configure the Cloud Replication settings, I'm getting error "10054".
The logs on the backend of the appliance show the following:

Code: Select all

4/15 17:59:33.164853 26 conf: TelnetListener::listenConnections: Accepted control connection from 192.168.241.140:51336.
4/15 17:59:33.224139 72 FileBrowser: *** CFileBrowser::parsePath: Could not create image : provided path has invalid extension!
4/15 17:59:33.224165 72 Srv: *** iScsiServer::list: Error parsing path: VSA Storage\mnt\storage1\
4/15 17:59:33.277638 72 Plugin: *** VtlDevice::sscControlRequest: Replication settings: send error!
4/15 17:59:33.307740 72 conf: ControlConnection::processConnection: Control connection closed.
The script I am running is attached (barely modified version of VTLReplicationSettings.ps1) and the console output is

Code: Select all

Name                   : vtl1
DeviceType             : VTL
DeviceId               : 0x0000000000BAC7C0
File                   : 
TargetName             : iqn.2008-08.com.starwindsoftware:starwindvsa-vtl1
TargetId               : 0x000000000091A580
Size                   : 0
CacheMode              : empty
CacheSize              : empty
CacheBlockExpiryPeriod : empty
Exists                 : True
DeviceLUN              : 0
IsSnapshotsSupported   : False
Snapshots              : 
SectorSize             : 
State                  : 0
Tapes                  : System.__ComObject
AvailableSlots         : 82
TransportSlots         : 1
DriveSlots             : 4
ImportExportSlots      : 3
StorageSlots           : 96
Slots                  : System.__ComObject
ReplicationSettings    : System.__ComObject
DriveType              : 5

Target           : 0
AccessKey        : 
SecretAccessKey  : 
RegionName       : 
ContainerName    : 
KeepLocal        : -1
KeepInCloud      : -1
KeepInStorage1   : -1
KeepInStorage2   : -1
DelayBeforeStart : -1
ServiceUrl       : 

Target           : 2
AccessKey        : <redacted>
SecretAccessKey  : <redacted>
RegionName       : us-east-1
ContainerName    : off-site-backup
KeepLocal        : 30
KeepInCloud      : 91
KeepInStorage1   : -1
KeepInStorage2   : -1
DelayBeforeStart : 0
ServiceUrl       : 

10054
10054
Target           : 1
AccessKey        : 
SecretAccessKey  : 
RegionName       : 
ContainerName    : 
KeepLocal        : -1
KeepInCloud      : -1
KeepInStorage1   : -1
KeepInStorage2   : 1
DelayBeforeStart : 0
ServiceUrl       : 
The forum will not let me attach the script so here it is:

Code: Select all

param($addr="starwindvsa", $port=3261, $user="<redacted>", $password="<redacted>",
	$deviceName="vtl1",
	$target=[StarWindVtlReplicationTarget]::REPLICATION_TARGET_S3,
	$accessKey="<redacted>",
	$secretAccessKey="<redacted>",
	$regionName="us-east-1",
	$containerName="off-site-backup",
	$keepLocal=30,
	$keepInCloud=91,
	$keepInStorage1=-1,
	$keepInStorage2=-1, 
	$delayBeforeStart=0,
	$serviceUrl)

Import-Module StarWindX

$server = New-SWServer $addr $port $user $password

try
{
    $server.Connect()

	$device = $null
		
	foreach($dev in $server.Devices)
	{
		
		if( $dev.Name.Equals($deviceName) -and $dev.DeviceType.Equals("VTL") )
		{
			$device = $dev
			break
		}
	}

	if( !$device )
	{
		Write-Host "Device '$($deviceName)' not found" -foreground red
		return
	}

	$device

	$settings = new-object -ComObject StarWindX.VTLReplicationSettings
	$settings

	$settings.Target=$target
	$settings.AccessKey=$accessKey
	$settings.SecretAccessKey=$secretAccessKey
	$settings.RegionName=$regionName
	$settings.ContainerName=$containerName
	$settings.KeepLocal=$keepLocal
	$settings.KeepInCloud=$keepInCloud
	$settings.KeepInStorage1=$keepInStorage1
	$settings.KeepInStorage2=$keepInStorage2
	$settings.DelayBeforeStart=$delayBeforeStart
	$settings.ServiceUrl=$serviceUrl
    $settings
	$res = $device.CheckReplicationCredentials($settings)
	$res
	$res = $device.ApplyReplicationSettings($settings)
	$res
	$device.ReplicationSettings
}
catch
{
    Write-Host $_ -foreground red
}
finally
{
	$server.Disconnect()
}
yaroslav (staff)
Staff
Posts: 2330
Joined: Mon Nov 18, 2019 11:11 am

Tue Apr 21, 2020 12:26 pm

Hi,

Sorry for the delayed response.
I had to double-check that everything is fine with the script with R&D.
There is a limitation coming from the system itself. See https://support.microsoft.com/en-my/hel ... ion-receiv for more info on the event.
koconnor
Posts: 3
Joined: Thu Nov 28, 2019 12:09 am

Tue Apr 21, 2020 1:28 pm

Hello,

Thanks for the response. It’s odd though because I am not using Windows 7 or Windows Server 2008 R2.

The VSAN appliance is CentOS and the VM running StarWind Management Console/StarwindX Powershell is Windows Server 2016. So do you still think the problem you linked is affecting me?

If so, I’m assuming it applies to the VM where I am running the Powershell script?
yaroslav (staff)
Staff
Posts: 2330
Joined: Mon Nov 18, 2019 11:11 am

Wed Apr 22, 2020 9:38 am

Greetings,
it applies to the VM where I am running the Powershell script?
Absolutely right...
Got an update from R&D recently. Currently, StarWind Cloud Replicator does not work for Linux-based version of StarWind.
That's where this error comes from.

I do not have an ETA when these 2 solutions will work together. Stay tuned!
koconnor
Posts: 3
Joined: Thu Nov 28, 2019 12:09 am

Mon Apr 27, 2020 3:10 pm

Okay, so the issue is actually in the Linux StarWind node itself, NOT the VM where I am running the Powershell script from (Windows)...

so if I attempt to set up a new StarWind VTL on Windows, it will work?
yaroslav (staff)
Staff
Posts: 2330
Joined: Mon Nov 18, 2019 11:11 am

Mon Apr 27, 2020 3:22 pm

Yes, you are right. On a Windows VM, that should work.

Let me know if it does not.
Post Reply