Thanks to all who replied and your patience while waiting for me to
respond as well... Let me address as many items as I can in the brief
amount of time I have to respond...
1st, we are paying for support of the version of networker we are using.
2nd, the newest nas filer we are backing up has 34 file systems attached
to it each file system has 51M+ files. We have decided to backup nas1
<--> nas2 and then backup from nas2 while it is in passive mode. It is
only 5.56 PB how long can this take to backup, 1 week... maybe 2?
/shakingmyhead
*** Note: the challenge we are having is the time it takes this
incredibly fast disk system to walk the directory for two of our backup
systems.
Our environment is Gi-normous (over 40,000 servers backed up globally)
as such, we are leveraging multiple backup solutions both hardware and
software. Because of the size and 24 hour business click we are in a
constant state of flux using Netbackup, Networker and TSM.
We have experimented and noticed that we have the same problems in
Netbackup that we have in networker but we do not have the same problem
with TSM, TSM seems to do a bit-block backup with no concern at all for
the index, until after the backup is done.
It is interesting and we are still working so many different performance
and trouble shooting concepts.
I do try to read this listserv mail as often as possible, I thank all
the contributors.
Semper fidelis, /ALE
Eddie.Albert AT att DOT net
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Yaron Zabary
Sent: Wednesday, May 11, 2011 8:12 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] 45M iNode FS backup?
On 05/10/11 23:06, jee wrote:
> On Tuesday 10 May 2011 18:52:48 Yaron Zabary wrote:
>> I think that any contemporary major backup software should be
able to
>> realize that the file system it is backing up is large (actually this
>> should be done for each directory)
>
> This is not about the size of the backup system. It is about the
amount of
> files that are on that file sysem and have to e opened individually
during
> backups (ultimately by the OS, not networker ).
I know. This is the usual file system traversal problem with many
files per directory.
>
>
> Snapimage is a practical solution for that. It does block-level
backups and
> avoids the too many system calls that would be required, during
file-level
> backups, to open and read each file that is to be backed up.
SnapImage need to be able to read the block device and understand the
file system. This means that SnapImage will be able to support only
certain file systems, so it might be able to backup ext3 but not ext4.
Also, some file systems, such as ZFS will not expose a block device
which it can work with.
>
> jee
>
> 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
--
-- Yaron.
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
----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the
intended recipient(s) and may contain information that is privileged,
confidential or proprietary. If you are not an intended recipient, please
notify the sender, and then please delete and destroy all copies and
attachments, and be advised that any review or dissemination of, or the taking
of any action in reliance on, the information contained in or attached to this
message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a
solicitation of any investment products or other financial product or service,
an official confirmation of any transaction, or an official statement of
Sender. Subject to applicable law, Sender may intercept, monitor, review and
retain e-communications (EC) traveling through its networks/systems and may
produce any such EC to regulators, law enforcement, in litigation and as
required by law.
The laws of the country of each sender/recipient may impact the handling of EC,
and EC may be archived, supervised and produced in countries other than the
country in which you are located. This message cannot be guaranteed to be
secure or free of errors or viruses.
References to "Sender" are references to any subsidiary of Bank of America
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal
Government Agency. Attachments that are part of this EC may have additional
important disclosures and disclaimers, which you should read. This message is
subject to terms available at the following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you
consent to the foregoing.
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
|