limitations in networker

I don't think there is a networker limitation. It depends on the licenses you have but ensure you don't chock your network with many clients.



Again, it should be the same as the max. no of devices as epr the configuration.



Should depend on the max. no. slot licenses or VTL capacity license you go for.



What type of limitation





What type of limitation.

No limit - except proper sizing of server.


Number of devices is limited within total nsrmmd limit.


None.


Compared to VTL? Speed and capacity. Additionally features like mirroring between VTLs (CDLs) and internal staging are making TLU looking more and more small.


Several different approaches are possible. It depends on environment.


None (except time effort required to create clone - with VTLs you can avoid that).

Thanks.

Regarding question 3, how many servers (or storage nodes) can you connect in 1 datazone?

If we take everything into account (1 server, storage nodes, dynamic drive sharing, VTL - with the capacity of creating as many tape libraries as required, etc),

do we still hit a limit on it?

Thanks again,
Kamal

How abt Q2?
2) How many maximum parallelism per node and per one datazone?
Power edition: maximum parallelism per one datazone:
Network edition:maximum parallelism per one datazone:

i mean to say this:

the hardware is from HP. the customer wants to configure 6 libraries in the VTL with 20,20,20,20,17,17 drives in each library. Then there is another VTL with 2 libraries in it with 19,19 drives in each library.

With this they will be using dynamic drive sharing with 2 backup server, 2 storage nodes and 55 dedicated storage nodes.

Will this hit the limitation of 512 nsrmmd processes?

does it make sense or am i confusing myself totally? sorry guys.

thanks for the help though.
Kamal

Message was edited by:
Kamal Thakor

Limit is hardware - software is just using it (so what you don't wish is to get software to HW limits). From what you have said it looks pretty simple and there should be no issue - but then again it depends on you HW power.

To drive such number of drives you will need alot of CPUs and probably HBAs as well... Each device will be 1 nsrmmd (only advanced file device takes 2). Depending of number of devices defined you will have to calculate totaln number of nsrmmds.

Hi,
I have an additional question relating to limitations in NetWorker around the number of files that it can back up

I have a system that has around 15 million files underneath the root of a drive.
the file names have all legal characters and are between 0Kb and 1Kb in size. the total data size is 3.5Gb

The only thing odd about the system is that the file system is formatted 1kb sectors rather than the defaults. System is W2003

NetWorker takes around 30+ hours to back it up but Dantz retrospect takes 10 hours.

are there any limits to how many of what type of files NetWorker can backup and s there an algorithm being compromised here within the code which is not allowing it to walk the file system correctly.

i have a meeting tomorrow morning which i would love to have an answer to

thanks

For such system I would use VSS client.

That's true, EMC people will usually suggest to use SnapImage in such cases.

VSS has no gains in such a file system that I know of, as VSS is still file-level backup. Can you explain why you think VSS would be a good idead here?
However, block-level backup should be benifitial here and SnapImage will flurish in such dense file systems.

All the best.

Hi Ross,

I was referring to snaps only where backup is done via snap (there is a new product called NetWorker VSS client for that). If one would go for tape backup I would rather have that migrated to Celerra and use VBB to make backup as that would give optimal performance (much better than SI).