Hi Michael,

What should also be nice you to give a look is the possibility
to overwrite/adapt the "critical volumes list". For sample,
the use of a directive like 

<< 'OSSR_E:\' >>
        +skip: *.*

or

<< '/' >>
        skip: OSSR_E

parsed by savegrp/save to not fork save session could be
an easy way to decrease DR backup size.

Cheers

Th

Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE
Backup/Storage & System Management

LE FOREM
Département des Systèmes d'Information
Direction Infrastructure

Boulevard Tirou, 104  Tel:    +32 (0)71/206730
B-6000 CHARLEROI      Mobile: +32 (477)/995319
                      Fax:    +32 (0)71/206199 
BELGIUM               Mail : Thierry.faidherbe<at>forem.be

-----Message d'origine-----
De : EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] De 
la
part de michael.jones2 AT EMC DOT COM
Envoyé : vendredi 19 août 2011 17:35
À : NETWORKER AT LISTSERV.TEMPLE DOT EDU
Objet : Re: [Networker] NW 7.6.2 and the DISASTER_RECOVERY: saveset

Understand the challenges.

One thing we are working on in the next release is the ability for file
level recoveries from DR backups and the ability to perform incremental
backups on top of those DR backups. This would solve your issues as while
E:\ is considered a critical volume for DR purposes, the DR backup would
support standard filesystem recoveries from this backup, avoiding the issue
of having to backup the user data on E:\ drive twice.

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Michael Leone
Sent: Friday, August 19, 2011 8:27 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NW 7.6.2 and the DISASTER_RECOVERY: saveset

> You could move the Lotus Domino service off of E:\ to solve your 
> problem.

Doubt it. I never set E:\Lotus\Domino as a VSS system file; it must have
done that when it installed. If so, then moving the data store will simply
change the entry in the system files (probably).

> If this drive and the Lotus service(s) were not protected, then there 
> is no way to complete a BMR recovery of the server, there would be 
> issues with Lotus.

I could re-install Windows, re-install Domino/Notes to same drive; do a
standard recovery of the E: drive. Domino doesn't make a whole lot of use
out of the registry; everything is in their own self-contained files. 
Pretty much the old fashioned way (i.e., the way it used to be with NW
7.5.2), and I'd still be able to do my FULL backups and AFTD storage without
needing multiple TBs of free space. This was never an issue with 7.5.2; it
only started with 7.6.2. So it's the way the DISASTER_RECOVERY: 
saveset works, since the VSS SYSTEM WRITER never used to save 300+G when I
was running 7.5.2.

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

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