Indexing question

[itig]

Hi,

Is it possible to start the "guest file system indexing" after the backup is taken? Or running in background, or directly from the backup file instead of the production server.
The reason is, it slow down the backup, especially in the case of a file server with 4 TB of data and reduce our backup window. And if the backup fail for VSS reason, or snapshot, we loose 1h or 2h of indexing for nothing.

thanks in advance.

[veremin]

Nope, it's not possible to run this activity either as background or post-job task.

Also, are using Enterprise Manager for granular item restores in your environment?

I'm asking since this functionality is used primarily for performing fast and accurate search for VM guest OS files via the Veeam Backup Enterprise Manager web UI. In other words, having "Guest Indexing" disabled, doesn't affect your ability to search/restore individual data via Veaam management server, only via Enterprise Manager.

Thanks.

[itig]

Yeah, I know. For a file server is very useful to be able to search for files.

Is it possible you can include indexing from backup file in future version?

Thanks

[skydok]

Hi,

I have a VM which is a Fileserver with Milions of Files 2.4TB of size.

Full Backup was 16 Hours - 2.4TB Data - 7 Hours Indexing
Incremental was 11:40 Hours - 41Gb - 11 Hours Indexing

The issue is of course because the Indexing is marked,but isn't there maybe a way to do somthing else?

1.Can i do an incremental Indexing someway?
2.Can i Do Job1 Only Backup and Job2 only indexing(diffrent time) ?

if section #2 can be done than the Indexing can be done only on weekends and isn't relevant for the whole week.

i am searching for a solution for one of my customers .

[foggy]

Indexing does not support incremental runs, full indexing is performed every time. Nor it can be performed separately from the backup job. If your server has millions of files, indexing could take a while, despite the fact that the process itself is pretty quick (Veeam B&R only reads the MFT table).

[skydok]

Foggy,
Saddly you didn't help
thanks for the Answer of course ,i guess the only way is

Job1 - Backup 3/4 Volumes with indexing
Job2 - Backup 1/4 volumes without indexing. (these volume doesn't need indexing but is 1.4 TB Big)

Am i correct of the workaround?

[foggy]

You can exclude the VM in question from indexing at the Guest Processing step of the job wizard (Advanced button). Hope this helps.

[skydok]

W'll i did somthing else, i excluded the Drive letter in the "exclude folders" of the specific VM ,which basiclly what i wanted to do.

So its the workaround i wanted.

[foggy]

Yep, should also work this way.