Guest file indexing - exclude drives?

[jja]

Hi!

We have a virtual fileserver in vmware which has 1 vmdk for os.
All the shared files are on direct iscsi connections.
Is it a way to exclude guest file indexing of these drives?
It seems to spend a lot of time indexing a vm which have no use for it.

-J

[Vitaliy S.]

Hi Jannis,

Excluding particular disks from indexing is not possible, however could you please tell me why do you want to index OS partition of the file server and not drives with files?

Thanks!

[jja]

Because the drives with files is not backed up with veeam, only the os drive is.
We have several iscsi luns connected directly to the fileserver, were all the data is stored.
These drives are backed up with TSM.

Indexing of those 30TB of data takes a lot of time.
The VM itself is only 140GB, and should not take a lot of time.

-J

[Vitaliy S.]

Yes, this makes total sense. I just thought that since system partition doesn't contain any files, there there is no need to index it. Anyway, thanks for the clarification!

[jja]

I'm thinking it would be smart to move the fileserver to its own backup job with indexing disabled.
Are there any ways to move the existing backups to the new job?
It's part of a job with 15-20 other vm's today.

-J

[Vitaliy S.]

The only way I can think of is to use backup copy job to synthetically create a VBK file for this very server and then create a regular backup job mapped to this VBK file. Should do the trick!

[foggy]

I'm thinking it would be smart to move the fileserver to its own backup job with indexing disabled.

You can disable indexing for the particular VM in the job in the advanced guest processing settings. In fact, you can even exclude folders there, so probably excluding corresponding disks by their letters will help to address your initial request.

[jja]

You can disable indexing for the particular VM in the job in the advanced guest processing settings. In fact, you can even exclude folders there, so probably excluding corresponding disks by their letters will help to address your initial request.

Thanks!
I've disabled indexing on the specific server.
It'll be fun to see tomorrow how it goes
Today it spent 1h12 minutes indexing on a job that took 1h23min total

-J