ADSM-L

Re: [ADSM-L] Journal backup

2012-02-08 07:19:45
Subject: Re: [ADSM-L] Journal backup
From: "Schaub, Steve" <steve_schaub AT BCBST DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 8 Feb 2012 07:10:09 -0500
We run journaling on all data drives by default for Windows, and rely on the 
monthly patch reboot to give us a periodic non-journal backup.

Steve Schaub
Systems Engineer II, Windows Backup/Recovery
BlueCross BlueShield of Tennessee

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Grigori Solonovitch
Sent: Wednesday, February 08, 2012 6:54 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Journal backup

It is enough to restart journal service periodically maybe by schedule. After 
restarting it TSM Client scans all files. I think it is easier than run special 
type of backups. We are using journal backup for all Windows servers without 
any problems and very seldom full scans.


Grigori G. Solonovitch
Senior Technical Architect  Ahli United Bank Kuwait  www.ahliunited.com.kw

Please consider the environment before printing this E-mail


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Hans Christian Riksheim
Sent: 08 02 2012 2:47 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Journal backup

Is it still a requirement that an incremental -nojournal backup should
be run once in a while to pick up the pieces left from the daily
journal backup?

In which case if I run a -nojournal every week, what I can tell the
customer what the expected RPO is? One week? One day if lucky?

Regards,

Hans Chr.


Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail 
message and any attachments hereto may be legally privileged and confidential. 
The information is intended only for the recipient(s) named in this message. If 
you are not the intended recipient you are notified that any use, disclosure, 
copying or distribution is prohibited. If you have received this in error 
please contact the sender and delete this message and any attachments from your 
computer system. We do not guarantee that this message or any attachment to it 
is secure or free from errors, computer viruses or other conditions that may 
damage or interfere with data, hardware or software.
-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm

<Prev in Thread] Current Thread [Next in Thread>