oadp
snapshot-location create
Create a volume snapshot
location.
Syntax
cpd-cli oadp snapshot-location create <oadp-snapshot-name> \
[--config=<map<key,value>>] \
[--labels=<map<label,label,...>>] \
[--provider=<backup-storage-provider-name>] \
# Global options
[--add_dir_header=true|false] \
[--alsologtostderr=true|false] \
[--cpd-namespace=<cpd-namespace>] \
[--kubeconfig=<kubeconfig-paths> \
[--log-level=info|debug|warn|error|panic|trace] \
[--log-backtrace-at=<source_code_file>:<line_number>] \
[--log_dir=<log_directory>] \
[--log_file=<log_file_name>] \
[--log_file_max_size=<uint>] \
[--logtostderr=true|false] \
[--namespace=<namespace-name>] \
[--one_output=true|false] \
[--skip_headers=true|false] \
[--skip_log_headers=true|false] \
[--stderrthreshold=<integer>] \
[--v=<integer>] \
[--verbose \
[--vmodule=<pattern1>=<n1>,<pattern2>=<n2>,<pattern3>=<n3>]
Arguments
Table 1: Command arguments
| Argument | Description |
|---|---|
<oadp-snapshot-name> |
The name of the volume snapshot location to create. |
Table 2: Global options arguments
| Argument | Description |
|---|---|
<trace-location> |
The stack trace location |
<severity> |
The log severity level |
Options
Table 1: Command options
| Option | Description |
|---|---|
--config |
The configuration key-value
pairs.
|
|
|
Display command
help.
|
--labels |
Labels to apply to the volume
snapshot location.
|
--provider |
The volume snapshot
provider name (for example, aws, azure, gcp).
|
Global options
You can also use the following global options with this command:
Table 2: Command global options
| Option | Description |
|---|---|
--add_dir_header |
Add the file directory to the
header of log messages.
|
--alsologtostderr |
Log to standard error as well as
files.
Note: This option has no effect when
--logtostderr=true. |
--cpd-namespace |
The IBM Software Hub namespace in
which the utility operates.
|
--kubeconfig |
Paths to a kubeconfig. Only
required if out-of-cluster.
|
--log-level |
The command log
level.
|
--log-backtrace-at |
When logging hits
<source_code_file> at line <line_number>, emit a stack trace. The default is any file at line
0.
|
--log_dir |
If non-empty, write log files in
this directory.
|
--log_file |
If non-empty, use this log
file.
|
--log_file_max_size |
The maximum size, in MB, that a
log file can grow to. If you specify 0, the maximum file size is
unlimited.
|
--logtostderr |
Log to standard error instead of
files.
|
--namespace
|
The namespace where OADP is
installed.
|
--one_output |
Specifies whether to only write
logs to their native severity level.
|
--skip_headers |
Specifies whether to avoid header
prefixes in log messages.
|
--skip_log_headers |
Specifies whether to avoid header
prefixes when opening log files.
Note: This option has no effect when
--logtostderr=true. |
--stderrthreshold |
Logs at or above the specified
severity threshold go to stderr. The threshold is used when you enable writing to files and
stderr.
|
--v
|
Number for the log level
verbosity.
|
--verbose |
Logs include more detailed
messages.
|
--vmodule |
A comma-separated list of
pattern=N settings for file-filtered logging.
|
Examples
Note: The following examples use the recommended installation environment variables.
It is strongly recommended that you use a script to create environment variables with the correct values for your environment. For more information, see Setting up installation environment variables.
- Create the
oadp-snapshot-namevolume snapshot for the AWS provider. -
cpd-cli oadp snapshot-location create <oadp-snapshot-name> \ --config=<map<key,value>> \ --provider=aws \ --log-level=debug \ --verbose