Yip

As I said, it is very quick to setup, doesnt affect other apps etc on the
disk. So I suggest you try it - perhaps on some other non busy system
(obviously running a disk based function will affect that systems
performance) ...

Riaan

-----Original Message-----
From: Narkinsky, Brian [mailto:Brian.Narkinsky AT DEP.STATE.FL DOT US]
Sent: Wednesday, April 28, 2004 10:44 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Large File system issues


How do you do this in Windows?

Just specify your saveset as \\.\Diskx ?

Brian

        -----Original Message-----
        From: Legato NetWorker discussion on behalf of Turner, Peter
        Sent: Mon 4/26/2004 9:36
        To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
        Cc:
        Subject: Re: [Networker] Large File system issues



        Does the block level backup require a volume shutdown or dismount?

        -----Original Message-----
        From: Riaan Louwrens [mailto:riaanl AT SOURCECONSULTING.CO DOT ZA]
        Sent: Monday, April 26, 2004 8:28 AM
        To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
        Subject: Re: [Networker] Large File system issues


        HI,

        A resolution that I have implemented a couple of time nows is to do
RAW
        filessystem backup (yes you can do this on windows as well).

        Essentially by specifying the \\.\X name of the drive. This will
then
do
        a block level backup of all the data at raw disk speed - normally
very
        fast. This is always a FULL backup of the WHOLE disk. So you would
want
        to keep your disk / partition size a close to the size of the actual
        amount of data (if possible) - perhaps create a dynamic disk that
you
        can grow if necessary.

        Typical example - we had a client that had 8GB of files numbering on
a
        10GB partition numbering close to 2 million and it took almost 2
days
to
        backup to a DLT7000. Doing a RAW backup this was done in under an
hour
        ... (10GB streamend to tape). Our client now does a FULL backup
every
        night - which he automatically restores to another machine (same
night)
        - just in case he might need to do file level recoveries. (see
below).

        Some restrictions though - as it is block level you cannot do file
level
        recoveries. (But if you only have 20 odd GB of data this shouldnt be
an
        issue - not sure what oen would do when you talk 100's of GB's).

        It "HAS" to be recovered to the same drive letter - so if you a
directed
        recovery you have to have a drive with the same drive letter (be it
C,
        D, E ... etc).

        Hope this helps!

        Regards,
        Riaan

        -----Original Message-----
        From: Tarjei T. Jensen [mailto:tarjei.jensen AT AKERKVAERNER DOT COM]
        Sent: Monday, April 26, 2004 7:32 AM
        To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
        Subject: Re: [Networker] Large File system issues


        "atif" wrote:
        >Are there any issues anyone can think of that I should consider?
Also,
        >we might be able to survive with 80GB fs. Any thoughts on that?
Thanks.

        We have used 300GB file systems with Windows 2000, but have decided
        against them because they take too long to back up and even longer
to
        restore. I'm not sure what size is favoured now.

        Smaller filesystems means the server can be backed up faster since
each
        filesystem is backed up seperately.


        greetings,

        --
        Note: To sign off this list, send a "signoff networker" command via
        email to listserv AT listmail.temple DOT edu or visit the list's Web 
site
at
        http://listmail.temple.edu/archives/networker.html where you can
also
        view and post messages to the list.
        =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

        ---
        Incoming mail is certified Virus Free.
        Checked by AVG anti-virus system (http://www.grisoft.com).
        Version: 6.0.668 / Virus Database: 430 - Release Date: 4/24/04


        ---
        Outgoing mail is certified Virus Free.
        Checked by AVG anti-virus system (http://www.grisoft.com).
        Version: 6.0.668 / Virus Database: 430 - Release Date: 4/24/04

        --
        Note: To sign off this list, send a "signoff networker" command via
        email to listserv AT listmail.temple DOT edu or visit the list's Web 
site
at
        http://listmail.temple.edu/archives/networker.html where you can
also
        view and post messages to the list.
        =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

        --
        Note: To sign off this list, send a "signoff networker" command via
email
        to listserv AT listmail.temple DOT edu or visit the list's Web site at
        http://listmail.temple.edu/archives/networker.html where you can
        also view and post messages to the list.
        =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

        --
        Note: To sign off this list, send a "signoff networker" command via
email
        to listserv AT listmail.temple DOT edu or visit the list's Web site at
        http://listmail.temple.edu/archives/networker.html where you can
        also view and post messages to the list.
        =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=



---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.668 / Virus Database: 430 - Release Date: 4/24/04


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.668 / Virus Database: 430 - Release Date: 4/24/04

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=