The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Anatoly (staff), Max (staff)
$settings.KeepInCloud - The time for saving in the cloud, days. The data will be removed from the cloud after this time expiration (It is working for all the types).Someone can explain what means the following parameters and possible values for the VTLReplicationSettings.ps1 (PowerShell Script)?:
$settings.KeepInCloud=
$settings.KeepInStorage1=
$settings.KeepInStorage2=
In the case of S3 you are making/changing the rule for the bucket, then Amazon is making everything by itself. The rule will work to all files in the bucket.Another thing. Should I create a Glacier Vault to move the files from S3 or do API this automatically? Beacause documentation says just about S3 bucket creation, but nothing about glacier.
I don't think this is the same thing. Veeam wouldn't be able to just create a new tape in the VTL. That is done with the powershell commands:Boris (staff) wrote:Check this option on the example of Veeam B&R:
https://www.starwindsoftware.com/resour ... e418c70ca9
You need to the screenshot at step 9 of the Veeam block. Veeam has got that setting, which seems to be exactly what you are looking for.
Code: Select all
$tapeType = [StarWindTapeType]::STARWIND_TAPE_ULTRIUM_LTO8
$tape = Add-VirtualTape -VTLDevice $device -tapeType $tapeType -tapeSize $tapeSize -maxDataFileSize $maxDataFileSize
Not sure if we are on the same page here. Bascially, I ran the Veeam job with no tapes in any slots but the ones that were in the offline shelf and I get a message from the Veeam job of "[Warning] Insert a tape to continue".Boris (staff) wrote:The Veeam feature I outlined does work for numerous customers that have it configured in their environments, and I do not have any grounds for suspecting this functionality to be faulty (unless this is specific to your particular environment). Have you tried configuring this before stating that "Veeam wouldn't be able to just create a new tape in the VTL"? If so, something is definitely wrong there, as it has been working flawlessly for hundreds of others.
With Veeam, you also have an option of ejecting the tape after the backup is completed, so you can later query the VTL device to get the list of offline shelf tapes as we discussed in https://forums.starwindsoftware.com/vie ... 954#p29954 I believe other backup software may have that functionality as well.
The reason this works is the setting in cloud replication on the StarWind side that I asked about in my previous post.Boris (staff) wrote:We are on the same page, but in its different parts, if I may say so...
First of all, you will need a tape available for Veeam to write backups to. Once this backup is successful, the tape gets ejected (if the corresponding option is enabled in the backup job config) and here VTL tape creation kicks in (again - if it is configured to do so). If you do not have any tapes online, this will never work, no matter how long you would wait for this.
This does work for everyone using StarWind VTL and Veeam. I am sure this will do so for you, too, once you configure everything properly. Just post back any questions you have after you follow the guide on configuring Veeam B&R to be used with VTL that I posted last week.
Code: Select all
Import-Module StarWindX
$server = New-SWServer -host 127.0.0.1 -port 3261 -user root -password starwind
try
{
$server.Connect()
#
# common parameters
#
$deviceName = "vtl1"
$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
}
catch
{
Write-Host $_ -foreground red
}
finally
{
$server.Disconnect()
}
Code: Select all
Name : vtl1
DeviceType : VTL
DeviceId : 0x0000004D8A100440
File :
TargetName : iqn.2008-08.com.starwindsoftware:veeambackup-targetvtl1
TargetId : 0x0000004D8A4DFA80
Size : empty
CacheMode : empty
CacheSize : empty
CacheBlockExpiryPeriod : empty
Exists : True
DeviceLUN : 0
IsSnapshotsSupported : False
Snapshots :
SectorSize :
State : 0
Tapes : System.__ComObject
AvailableSlots : 96
TransportSlots : 1
DriveSlots : 4
ImportExportSlots : 3
StorageSlots : 96
Slots : System.__ComObject
ReplicationSettings : System.__ComObject
DriveType : 8
Target : 0
AccessKey :
SecretAccessKey :
RegionName :
ContainerName :
KeepLocal : -1
KeepInCloud : -1
KeepInStorage1 : -1
KeepInStorage2 : -1
DelayBeforeStart : -1
ServiceUrl :
Hi Michael,Michael (staff) wrote:Hello willn333,
The option "Create new empty tapes automatically when existing tape removed from VTL for replication." can be changed in VTL device configuration file. For example in my case it's located here: "E:\VTL\VTL.swdsk"
Just stop StarWind Virtual SAN and CloudReplicator services, open VTL.swdsk, locate the line "<createTapeOnExport>false</createTapeOnExport>", change "false" to "true", save file and start services back.
Let us know about the result.
That you can tune in the AddVirtualTape.ps1 script. See the lines to edit in the image below.- each new tape creates with default maximum tape size and default part size.
Well, these parameters cannot be modified in StarWindX yet."<createTapeOnExport>true</createTapeOnExport>" reverts to "false" state
Sorry, got your question wrong. R&D guys are planning to modify the script so that tape that is created has identical properties as the offloaded one.But such modification of AddVirtualTape script doesn't affect an automatic tape creation after the export.