Re: [Networker] Window 2008 memory and logs

Hello,
Please review storage node  or snapimage ( if still available) option for 
this client.

How I can enable local logging on the EMC networker client.
        If you run the client by script, then -v ( each extra v will 
increase the logging level) with the save       cmd will do it ( logs will 
go to savegrp log)or you can do verbose logging for the group. ( I would 
be      very careful with either option, as the log file fills up, it 
could adversely impact your backup &            server performance, you 
will get failure messages without extra logging ( i.e open files etc)
- Is it possible not to dump the full filesystem for each drive prior to 
backing up data?
        You will need to look into Native OS capabilities, i.e VSS, also 
look into change journal to make use of         it's capabilities
- Is it necessary to put a hughe amount of physical memory in the server 
for backup purposes only?
        I don't think so, however, expect backups to run very long time, 
unless you breakup the data in various  saveset and configure Legato 
backups to be spread out. ( How much data and files are you referring too 
?)
If you cannot get SN capabilities , try and serrate file system if 
possible to different logical disk & spread out your backups, this way you 
may gain slight advantage on read access & add  a robust raid controller , 
optimized for read. ( This are optional steps and will only go so far)
Does your backup go to tape or VTL ? You may gain slightly better 
performance if you use disk or VTL backups vs Tape ( again few other may 
disagree)
HTH



aka004db <networker-forum AT BACKUPCENTRAL DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
03/18/2009 08:00 AM
Please respond to
NETWORKER AT LISTSERV.TEMPLE DOT EDU


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Window 2008 memory and logs






Dear All,

I'm working on getting a Windows 2008 x64 server with a very large file 
system to backup with EMC networker. My conclusions so far watching the 
performance counters and tools on the server:
- For each saveset a save.exe process starts
- Each save.exe process creates a complete directory listing in memory 
regardless of the path to be backed up
- There is default no log locally on the Windows 2008 server.

As this is a server with a very large filesystem, the complete directory 
listing for each save.exe process will put several GBs of data into 
memory, causing memory paging and performance issues. In the end the 
backup completely fails for all savesets other than some system VSS save 
sets.

I'd like to know:
- How I can enable local logging on the EMC networker client.
- Is it possible not to dump the full filesystem for each drive prior to 
backing up data?
- Is it neccesary to put a hughe amount of physical memory in the server 
for backup purposes only?

Cheers

+----------------------------------------------------------------------
|This was sent by arjan.kauffman AT tele2 DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type 
"signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER