#1 2019-11-12 11:03:59

marco
Member
Registered: 2018-11-29
Posts: 8

"block size of this repository is 0"

Hi,

I have another odd issue, I have been successfully running xsibackup-dc on one server for a few weeks now, so decided to try the other licence on another server.

Setup is the same, simplest backup possible, backing up to an NFS share running on an Ubuntu linux machine which is mounted as a datastore 'backup'. So, the VMWare machine 'sees' the target as just another datastore*.

*Note: This target is actually a different machine, though configured the same as the previous tests (one is in our office for testing, the other is located in our datacentre).

Tried mounting as NFS3 and NFS4, both with similar results.
The odd thing being, if I run xsibackup-pro on that host, then it runs fine.

Command line
./xsibackup --backup  "VMs(RUNNING)"  "/vmfs/volumes/backup"  --backup-how=Hot  --use-smtp=1  --mail-to=noc@xxxxxxxxxx

Error

(c)XSIBackup-Datacenter setting repository at /vmfs/volumes/backup
-----------------------------------------------------------------------------------------------------------------
2019-11-12T09:31:16 | Error code 2825 at file common.c, line 2825
Error description: the block size of this repository is 0, you can't use a block size of 1048576 to backup to it.
-----------------------------------------------------------------------------------------------------------------
2019-11-12T09:31:16 | Error code 2023 at file xsibackup.c, line 2023
Error description: could not verify/create repository, is target a repository?
-----------------------------------------------------------------------------------------------------------------

Immediately afterwards, I can list the directory, which is present and looks okay (we can see backups made by -Pro)...

ls /vmfs/volumes/backup/
20191108003012  20191109001514  20191109003013  20191110003011  20191111001514  20191112001514  20191112092641  20191112093111 
20191108003013  20191109003012  20191110001513  20191110003013  20191111003014  20191112003013  20191112093006

Offline

#2 2019-11-12 17:07:48

admin
Administrator
Registered: 2017-04-21
Posts: 1,385

Re: "block size of this repository is 0"

You can't use a Pro repository as a backup target for DC.
You shouldn't make asumptions like that, you could loose your data.
We make it clear that (c)XSIBackup-DC is a different product, it uses a different compression algorithm and, although the repository folder structure is similar, that does not mean you can mix data from different sources into a single repository.

Offline

#3 2019-11-13 08:38:46

marco
Member
Registered: 2018-11-29
Posts: 8

Re: "block size of this repository is 0"

Hi,
Thanks for your reply.

I may have used confusing terms in my posting.
I understand that I can't mix -dc and -pro versions when storing backup data to the same place (i.e. the same named directory).
However, what I intended to say, was that I am storing all backups to a Linux machine which has an NFS mount of /var/data/nfs, this nfs directory is then mounted as /vmfs/volumes/backup on the ESXi hosts.

Each backup run is stored in the 'dated' directory from when the backup was run... so in this case under each dated folder there should be no mixed versions.

I do have this apparently working on our local 'test' storage server.

For example, backups stored under /var/data/nfs/20191113001513 made with -dc, and backups stored under /var/data/nfs/20191113021512 made with -pro

I don't want to delete all my historical backups in dated directories before switching to -dc

-dc should 'see' my datastore named 'backup', create a new dated directory, and then write a complete (-dc only) backup to that area?

Maybe I should buy an additional -dc licence and switch all at once?

Thanks for your help so far.

Offline

#4 2019-11-14 02:17:46

admin
Administrator
Registered: 2017-04-21
Posts: 1,385

Re: "block size of this repository is 0"

We are afraid you are not fully comprehending how (c)XSIBackup-DC works, as commented quite similar to what --backup-prog=XSITools:z does in Pro version.

(c)XSIBackup-DC stores backups to a deduplicated repository, the root of the backup repository are not the timestamped folders, but it's one level up.

If you backup to let's say /vmfs/volumes/backup/myDC-repo, the program will create the data folder the .xsitools file and the timestamped folders under it.

/vmfs/volumes/backup/myDC-repo
/vmfs/volumes/backup/myDC-repo/data
/vmfs/volumes/backup/myDC-repo/.xsitools
/vmfs/volumes/backup/myDC-repo/20191113001513
/vmfs/volumes/backup/myDC-repo/20191114001513
/vmfs/volumes/backup/myDC-repo/20191115001513
/vmfs/volumes/backup/myDC-repo/20191116001513

In case you are backing up to /vmfs/volumes/backup/ you are using the root of the volume as the root of the repository and you are indeed mixing both programs output.

Offline

#5 2019-11-14 09:11:42

marco
Member
Registered: 2018-11-29
Posts: 8

Re: "block size of this repository is 0"

Thanks again for the reply.
I understand now...
So, to have mixed versions of XsiBackup, I will have two directories on my target
\var\data\nfs\backups-with-pro
\var\data\nfs\backups-with-dc

Of course, this is for testing only... I due course I will migrate so that we are using -dc only.

Thanks for the clarification

Offline

#6 2019-11-14 12:41:55

admin
Administrator
Registered: 2017-04-21
Posts: 1,385

Re: "block size of this repository is 0"

Yes, just use an additional directory to differentiate contents, or one more to have multiple repositories of each kind.

Offline

Board footer