Cloud Edition Command Line File Listing

[markinsocal]

I'm evaluating Veeam Cloud Ed. I want to get a list of files in an account. I enter the following on the command line:

cbb list -a "AX_Daily" -f
(where "AX_Daily" is my account name)

I get back:
Veeam Cloud Backup Command Line Interface started
Connection settings is OK

So I also tried:
cbb list -a "AX_Daily" -f *.vbk

I get back:
Veeam Cloud Backup Command Line Interface started
Connection settings is OK
ERROR: File '*.vbk' was not found

So I also tried:
cbb list -a "AX_Daily" -f AX-Imagestore01-Drive-H-2014-07-16T230132.vbk
(I know that vbk file is there)

I get back:
Veeam Cloud Backup Command Line Interface started
Connection settings is OK
ERROR: File 'AX-Imagestore01-Drive-H-2014-07-16T230132.vbk' was not found

Veeam and Cloudberry docs are no help. Any ideas?

[veremin]

Have you tried to input the directory, not the file name, using -d switch? What happens if after -f switch you enter the full file path, not just its name? I've checked it briefly and with full file path being input after -f everything seems to be working good. Thanks.

[markinsocal]

I'm not sure what the full path or directory would be at Glacier? From my perspective, I setup a "vault" at Glacier. In VCE I setup an "account" pointing to the vault. My job sends a file to the account.

How would the path or directory be properly expressed?

[veremin]

Unfortunately, I don't have any backup plain pointed to Glacier at hand. I only have a plan pointed to local file system storage. I was able to make everything work, using either directory parameter or file parameter with whole file path being specified.

Anyway, you can open a ticket with our support and see whether they will be able assist you with that.

Thanks.

[veremin]

Followup: There is nothing special about Glacier, as you have to input a whole directory or a file path. In order to do so, kindly, go to backup storage, drill down to a given file, and copy/paste a path. Thanks.

[markinsocal]

I was instructed by support to download Cloudberry Explorer (free), to view the contents of Glacier. I did and it is showing nothing is there. The history tab in VCE shows files uploaded successfully and the Backup Storage tab in VCE shows files & folders. I looked at VCE log and it looks normal to me. Here's an excerpt. I copied everything between two "Chunk..is ready for transfer" entries, showing multiple "uploaded" messages:

Code: Select all

2014-08-01 01:29:33,952 [CL] [8] INFO  - Chunk 1281 for Mars2014-07-31T233113.vbk is ready for transfer. Size: 16777216. Start offset: 21474836480
2014-08-01 01:29:34,031 [S3] [7] INFO  - Part 1279 starting uploading. Upload id: T1W8eWdaUG6tToJjw-CVy-WA142MWPrArdxKOIb__alIxgCdUuTQrUagt91k44UDOCS1idmOmg7WaM5evg9MOrmiqgXf
2014-08-01 01:29:37,734 [S3] [11] INFO  - Part uploaded. range: bytes 21374173184-21390950399/*, length: 16777216
2014-08-01 01:29:37,734 [S3] [11] INFO  - Part 1275 uploaded, uploadID: T1W8eWdaUG6tToJjw-CVy-WA142MWPrArdxKOIb__alIxgCdUuTQrUagt91k44UDOCS1idmOmg7WaM5evg9MOrmiqgXf, region: US, vault: Static, starting offset: 21374173184, length: 16777216
2014-08-01 01:29:37,734 [Base] [11] INFO  - MemoryManager: memory stream disposed. Name: 8cf4b2d2-7140-4fb5-86a7-6662915b374e. Initial size: 16777216, Current size: 16777216, Created: 08/01/2014 01:29:05.
2014-08-01 01:29:37,734 [Base] [11] INFO  - MemoryManager: StatInfo: Memory: reserved: 117637120, used: 117637120, Disk: reserved 0, used: 0.
2014-08-01 01:29:37,749 [Base] [8] INFO  - MemoryManager: MemoryStream created. Name: e4b9e47e-18d0-4f50-af11-a03af7404827. Initial size: 16777216, Current Size: 16777216
2014-08-01 01:29:38,140 [CL] [8] INFO  - Chunk 1282 for Mars2014-07-31T233113.vbk is ready for transfer. Size: 16777216. Start offset: 21491613696

[markinsocal]

Additionally, I just transferred a small file using Cloudberry Explorer and it reports that it's there. I closed and reopened app. File still there. Others are empty. BUT, I just noticed folder sizes of my vaults are hundreds of GB's, which is as it should be. It's as if the VCB files are filtered out or hidden.

[veremin]

Have you tried to go to the "Backup Storage" node and check the file path there (Disk:\Folder\File)? Thanks.

[markinsocal]

Yes. See 5:38a post

[veremin]

Given that Backup Storage tab does show the files and directories, why not to copy the file path/directory (C:\Backup\...) from there and use it later in commandline utility? Thanks.

[markinsocal]

Tried these commands just now. "Static" is account name. The file & folder were recorded good in history. The source file is no longer present. This reminds me of the hidden file attribute, where if I apply that attribute to a file somewhere, it doesn't show up in a regular DIR command. The fact that Cloudberry explorer can't see VCE files, but can see it's own file copies, may mean that the two companies have an agreement that Cloudberry won't allow interaction with VCE files. VCE command line may not have been changed to allow viewing the files? An engineer on the Veeam/Cloudberry team should know if this is true.

Code: Select all

cbb list -a Static -d z:\veeam\mars_1
Veeam Cloud Backup Command Line Interface started
   Connection settings is OK
ERROR: Folder z:\veeam\mars_1 was not found in cloud storage

cbb list -a Static -f z:\veeam\mars_1\*.vbk
Veeam Cloud Backup Command Line Interface started
   Connection settings is OK
ERROR: File 'z:\veeam\mars_1\*.vbk' was not found

cbb list -a Static -f z:\veeam\mars_1\Mars2014-07-31T233113.vbk
Veeam Cloud Backup Command Line Interface started
   Connection settings is OK
ERROR: File 'z:\veeam\mars_1\Mars2014-07-31T233113.vbk' was not found

cbb list -a Static -f \\storage2\e$\veeam\mars_1\Mars2014-07-31T233113.vbk
Veeam Cloud Backup Command Line Interface started
   Connection settings is OK
ERROR: File '\\storage2\e$\veeam\mars_1\Mars2014-07-31T233113.vbk' was not found

[veremin]

Not sure what might be wrong in your case. Below is there procedure we've followed to make cloud commands work. Please, try to do the same or repeat in case you've done it already and see whether the issue persists:

1) Backed up a file to Glacier and named account "Glacier". The file originally resided in "C:\backup\VeeamConfigBackup\PM-2012R2\" folder.
2) Made sure that the file was reflected under "Backup Storage" tab.
3) Went to a console and typed "cbb.exe list -a "Glacier" -f C:\backup\VeeamConfigBackup\PM-2012R2\PM-2012R2_2014-08-05_14-31-21.bco".

Thanks.

[markinsocal]

SOLVED: WITH CAVEATS

That test worked for me. Then I went back and tested with some past files that I had uploaded and discovered some things:

1. The cbb list commands only work with drive letters. UNC paths don't work (please confirm).
2. You cannot filter a list with wildcards (e.g. "*.vbk"). So all you got is a full unfiltered list using -d
3. Cloudberry Explorer doesn't actively show the contents of Glacier. It works off of it's cache. When you first install, it shows no contents. You have to "Get Inventory" which takes 4 hours because, "this is how Glacier works" (https://forums.aws.amazon.com/thread.js ... dID=104756 , 9/19/12 @ 12:36AM)

#3 above led me to believe that the cbb.exe isn't actively checking Glacier when executed, but looks at it's cache like Cloudberry Expl, else it wouldn't get an answer for 4 hours. So I did a test. I did a known good -d command before and after disconnecting the network from my machine. Returned result was the same both times, showing "Connection settings is OK", and the contents of the folder. This is pretty misleading as there is no connection made to Glacier in this utility and it is not an authoritative list of what's at Glacier if you are using any other tools that might change the contents of your vaults, for instance Cloudberry Explorer etc.

[markinsocal]

UNC PATHS support discovered:

You can use cbb to show the files you sent up using UNC source. You have to use a special undocumented format.

What does NOT work: C:\Program Files\Veeam\Cloud Backup>cbb list -a static -d \\storage2\e$\veeam\Mars_1

What does work: C:\Program Files\Veeam\Cloud Backup>cbb list -a static -d storage2:e$\veeam\Mars_1

Figured that out on my own. Hope it helps somebody.

[veremin]

It really does. Thank you Mark for taking your time and updating the topic with your discoveries; highly appreciated.