06-08-2020 03:28 AM - edited 06-08-2020 03:29 AM
Hello;
I did some research but I couldn't find a clear answer. What are the disadvantages of this feature(enable file recovery ftom VM) on the master?
if this is the case, I want to create two different policies enable file recovery option VMS and the others.
Solved! Go to Solution.
06-09-2020 03:20 AM - edited 06-09-2020 03:25 AM
I dont think there is any disadvantage unless you dont want the ability to recover files from it.
The Catalog will have file history as usual for oher machines in addition to Snapshot Information.
The only advantage I can think of is Catalog will not index its files which will save Caalog space (Theoritically )
But a Veritas Engineer will be at a better position to answer this
Regards
06-08-2020 10:26 AM
m sorry but why do you think there will be any disadvantages on Master ?
I have been using this option ever since it made available by Veritas and never had issues.
06-08-2020 11:46 AM
Hi
I think NBU catalog migth be bigger when this is enabled... but in now a days no one is considering this as down side - thanks to storage being cheaper and cheaper...
06-09-2020 02:51 AM
you will have more disadvantage if you create seperate policy for file recovery and for VM, as the backup data has to travel twice from source to Netbackup, it will put load on network, Netbackup master & media server and in catalog, its simply doubles the work. it is not a best practice and i highly discourage to doing it, unless you have a better justification for server to server basic.
06-09-2020 03:20 AM - edited 06-09-2020 03:25 AM
I dont think there is any disadvantage unless you dont want the ability to recover files from it.
The Catalog will have file history as usual for oher machines in addition to Snapshot Information.
The only advantage I can think of is Catalog will not index its files which will save Caalog space (Theoritically )
But a Veritas Engineer will be at a better position to answer this
Regards
06-09-2020 08:17 AM
@iVaibhav is correct - there will be a saving in size reduction of the NetBackup Catalog.
Catalog size can be estimated here:
https://www.veritas.com/support/en_US/doc/18716246-126559472-0/v41242670-126559472
.
Certainly there is an argument to not indexing VM backups if you do not have to. Why consume resources when you do not need to. Whether a VM backup has its contents indexed or not will have no effect upon the elapsed time duration of whole VM restore.
06-09-2020 08:49 AM - edited 06-09-2020 08:50 AM
06-10-2020 06:28 AM
Thank you very much for your replies. Yes actually my real concern is catalog backup size and also reduce all possible load on master server.
06-10-2020 12:02 PM - edited 06-10-2020 12:03 PM
Hello @quebek , i saw advices about after the certain catalog backup size create new netbackup domain. I try to prevent my environment to need of new netbackup domain. Many thanks.
06-10-2020 12:29 PM
Good to know @MustafaAogluGT
Please Mark an answer as a solution so that this Thread can be closed and concluded.