< Back

Remove-ArchivialNetworkSource

Fri Jan 10, 2020 8:44 pm

NAME Remove-ArchivialNetworkSource



SYNOPSIS

Removes the specified Network Source.





SYNTAX

Remove-ArchivialNetworkSource -SourceID <int> [<CommonParameters>]



Remove-ArchivialNetworkSource -NetworkSource <NetworkSourceLocation> [<CommonParameters>]





DESCRIPTION

A Network Source is a folder on your network (referenced by UNC Path) that Archivial backs up and automatically

monitors for new and updated files.



Removing a Network Source means that new or updated files from that location will not be backed up anymore, but

existing files already backed up to cloud storage will remain.



To view existing Network Sources, run Get-ArchivialNetworkSource. This command supports piping from

Get-ArchivialNetworkSource or manual invoke from the specified source ID.





PARAMETERS

-SourceID <int>

Specify the ID of the Network Source to remove.



Required? true

Position? named

Default value 0

Accept pipeline input? false

Accept wildcard characters? false



-NetworkSource <NetworkSourceLocation>

Specify the object (from pipeline) to remove.



Required? true

Position? named

Default value

Accept pipeline input? true (ByValue)

Accept wildcard characters? false



<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug,

ErrorAction, ErrorVariable, WarningAction, WarningVariable,

OutBuffer, PipelineVariable, and OutVariable. For more information, see

about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).



INPUTS

ArchivialLibrary.Folders.NetworkSourceLocation

Specify the object (from pipeline) to remove.





OUTPUTS



---------- EXAMPLE 1 ----------



C:\\> Remove-ArchivialNetworkSource -ID 3



Removes the Network Source with the specified ID.



---------- EXAMPLE 2 ----------



C:\\> Get-ArchivialNetworkSource | Where Path -like "*\\\\drobo-nas\\documents*" | Remove-ArchivialNetworkSource



Removes any configured Network Source that matches a path containing the specified filter (using the pipeline

scenario).





RELATED LINKS