In my experience, I just leave my house exchange server on for long
enough and that'll make it go splat :-)

-----Original Message-----
From: Mark Harford [mailto:[EMAIL PROTECTED]]
Sent: 29 October 2001 10:03
To: Exchange Discussions
Subject: RE: How to break Exchange in the Lab [Was: NTBackup]


Another good one is to let your IS and/or logfile space run out very
rapidly
from a mail loop (use blat or the reskit simulation tools for the loop).
See if you really can get that server back up and running with some
extra
disks within your SLA period & the mail loop cleared up before it goes
down
again!


-----Original Message-----
From: Martin Blackstone [mailto:[EMAIL PROTECTED]] 
Sent: 28 October 2001 18:35
To: Exchange Discussions
Subject: RE: How to break Exchange in the Lab [Was: NTBackup]


You could also use a hex editor to fsk up some bits and bytes on the IS.
Take some big chunks out

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Listserver,
Exchange MSER:EX
Sent: Sunday, October 28, 2001 8:52 AM
To: Exchange Discussions
Subject: RE: How to break Exchange in the Lab [Was: NTBackup]


If you mess around with Disk Caching setting for your array controller
and
fake a power failure, or turn on NT disk compression on your database
drive,
you should see the dreaded -1018 error on your next backup.

Steve Smith MCSE 
Information Technology Services Division 
Ministry of Management Services 
Province of British Columbia 
email: mailto:[EMAIL PROTECTED]          
Phone: (250) 387-8698 



-----Original Message-----
From: Sanborn, John [mailto:[EMAIL PROTECTED]] 
Sent: Saturday, October 27, 2001 1:01 PM
To: Exchange Discussions
Subject: RE: How to break Exchange in the Lab [Was: NTBackup]


Hmmm ... Had not run across that yet.  And here I thought I'd been
checking
out all the resources from the list.  :-(  

Cool stuff in there and in the directory above it:
http://www.microsoft.com/Exchange/techinfo/administration/55/ 

It maybe in there [only took a quick peek], but what I want to do is
find
ways to realistically break a lab machine that would mimic real-life
problems that require the use of the tools in the whitepages and
techniques.

-----Original Message-----
From: Drewski [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 27, 2001 12:36 PM
To: Exchange Discussions
Subject: RE: How to break Exchange in the Lab [Was: NTBackup]


go find the disaster recovery whitepapers.

http://www.microsoft.com/Exchange/techinfo/administration/55/BackupResto
re.a
sp
http://www.microsoft.com/Exchange/techinfo/deployment/2000/E2Krecovery.a
sp

Keep them close to your heart at all times.   The methods there are like
the
Ten
Commandments.

-- Drew
********************************
Visit http://www.drewncapris.net!  Go!  Go there now!
Never laugh at anyone's dreams. People who don't have dreams don't have
much.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Sanborn, John
Sent: Saturday, October 27, 2001 2:23 PM
To: Exchange Discussions
Subject: How to break Exchange in the Lab [Was: NTBackup]


Thanks to everyone and MSKB[1], I now have backups that I KNOW are good.

Next step now, is to learn how to fix Exchange.  I know there are a few
million ways to break Exchange, but what would be the best for learning
the
repair tools in a lab environment?

The hardware stuff 'should' be straight-forward.  Break it - ID it -
Repair/
Replace/ Restore - Reboot. The software and DB corruption would need to
be
more careful to avoid getting into a 'Restore is only option' situation.

Any Ideas?

Thanks
John

[1] Q146306 - Exchange Server Backup & Restore Procedures
    Q179308 - How To Verify Exchange Online Backups
    Q152313 - Using the AT Backup Command with Microsoft Exchange

-----Original Message-----
From: Seitz, Peter [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 26, 2001 10:52 AM
To: Exchange Discussions
Subject: RE: NTBackup


Our bat file reads:  "ntbackup backup z:\exchsrvr\tracking.log DS
\\curly IS
\\curly  /b /hc:on /t Normal /l C:\winnt\backup.log ntbackup eject

z:\exchsrvr is because we are a clustered enviroment, hence Larry, Moe,
Curly, Curly being the virtual node, Larry and Moe are the actual nodes.
Our
only problem has been lately is that our store has exceeded tape
capacity,
and we have to click on "OK" the next morning to finish up the backup on
the
next tape.

sorry, no haiku.


Peter Seitz
Operating Systems Analyst
Cubic Corporation
San Diego, Ca. 92021
(858) 505-2724


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 26, 2001 10:25 AM
To: Exchange Discussions
Subject: NTBackup


Iron Chef Haiku [1]
Subtle textures not seen here
And no steeenking rhymes

ntbackup rules
I should say in most cases
Small vexing problem

on just one server
all drives don't go on one tape
space not the issue

when each drive is done
wants new tape for the next drive
command line follows

ntbackup backup c: d: e: ds \\server is \\server /v /r /b /e /l
"d:\backup\backup.log" /hc:on /t normal

/v verify
/r restricts access
/b backs up local registry
/e log includes exceptions only
/l backup log filename
/hc:on Hardware compression on
/t normal (full) backup



not using the slash-a
backup acts like it is there
three drives specified


/a
Causes backup sets to be added or appended after the last backup set on
the
tape. When /a is not specified, the program  overwrites previous data.
When
more than one drive is specified but /a is not, the program overwrites
the
contents of the  tape with the information from the first drive selected
and
then appends the backup sets for the remaining drives.


Exchange alone works
Combination doesn't work
Drives alone bite too

NTSP6
Ex55Sp4
hotfixes as well


makes no difference
running comand line or bat
any help out there?

Thanks,
Paul

[1] in Japanese, the word "haiku" has 3 syllables = ha-i-ku  deal with
it
         -Michèle Sharik, October 26, 2001

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]


This e-mail, and any attachment, is confidential. If you have received
it in error, please delete it from your system, do not use or disclose
the information in any way, and notify me immediately. The contents of
this message may contain personal views which are not the views of the
BBC, unless specifically stated.

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to