Re: Backing up SQL server with Retrospect

[Serge Paulus]

since you can't backup an opened file in NT, what we do is manually/automatically dump 
and save databases with SQL entreprise server.

On mercredi 9 août 2000, Doug Clements <[EMAIL PROTECTED]> wrote:
>Greetings,
>Just wondering if anyone was already backup up a Microsoft SQL server 
>with Retrospect, and how well it works.
>
>Thanks..
>
>--Doug
>
>
>
>--
>--
>To subscribe:[EMAIL PROTECTED]
>To unsubscribe:  [EMAIL PROTECTED]
>Archives:
>Problems?:   [EMAIL PROTECTED]
>
>




--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: Silly Newbie Questions

[Keepsake]

Ed Hintz wrote:
> Being that OS X has a rather incestuous relationship with NetBSD, and
>that Dantz is publicly working on OS X support, 'tis but a small step to
>NBSD and OBSD... One would hope such a step would take place, to be sure...

Actually, it is FreeBSD that Apple has utilized for OS X:


Of course, I believe a reasonably bright programmer could create a 
cross Un*x platform solution, so it really would just be one product 
for Linix/BSD. I know if I get my way to set up an OpenBSD server, 
I'd love to have Retrospect backing it up.
-- 
Eric Zylstra
[EMAIL PROTECTED]


--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

freezes in Mac while backing up....

[Andrew Stein]

Hello, this is my first posting to this mail 
list.
 
I have recently purchased Retrospect Workgroup 
Backup 4.3 to backup a G3 server onto a Seagate Scorpion 24 (STD224000N-SB) tape drive, and I have only one problem with 
it
The backup run of any script ( or any backup 
attempt at all) will freeze at a random point during execution, with the 
software running and the tape drive read light off, and remain so forever.  
If the system is loaded without extensions, everything works fine, the script 
run perfectly. 
 
The obvious problem I have been trying to fix is 
some sort of conflict with the extensions, and I have been removing ones from 
the extensions folder and disabling them to attempt to find the one or ones 
causing the problem. This has not worked, and I am honestly 
stumped.
 
Anyone have any ideas?
 
 
-Andrew Stein

Re: Newcomer Questions

[Matt Barkdull]

>* DAT Tape drive - DDS3 or DDS4 attached to a PowerMac 7300, 
>probably Sony (or LaCie which I think uses a Sony mechanism), no 
>particular reason to go with Sony.
>* Retrospect 4.3 with clients on each of the Macs.

I've had a lot of problems with the Tape changer put out by Sony. 
The one I have is 8 tapes (or 7+cleaning, but Retrospect for Mac 
doesn't support cleaning tape!!)

I use to back up about 60 Macs using two DDS3 tape changers by Sony. 
That got to be way to much of a burden because of tape hassles, Tape 
Changer problems.  I used nothing but Sony tapes in these units as 
the Maxell, HP, and other brands had an average tape failure of 1 in 
8.

Even with Retrospect set on "Skip bad media" it didn't work 100%

My solution was to get a single Quantum 7000 DLT.  Bang for the buck, 
this drive has been working for me for over a year and I've never had 
a problem related to the drive or any of the tapes.  I've restored 
data several times as well to both Macs and NT machines.  All of them 
worked without a flaw.  I currently only backup about 25 machines 
every night.

Our department probably has about 10 of the DAT tape drives sitting 
around now because they don't work properly.  I know that two of the 
tape changers are dead and would cost $700 to fix, and the other two 
are only being used for single machine backups now.  We got a DLT 
tape changer that cost a small fortune, but I think in the 2 years it 
has been operating, it has already paid for itself.  It is connected 
to an NT box and except for Adminstrative problems with getting the 
right software, it has been flawless as well.  (They started with 
some other over priced software and it was very hard to tell if it 
was even working, but now use Retrospect)

BTW - in all, our department owns 6 of the Sony Tape Changers.  2 I 
know for sure are dead, 2 are being used, and the other 2 are on a 
shelf, I don't know status.   We also owned two HP 18000, 6 tape tape 
changers.  Those both work and are now doing single NT Server backup, 
directly connected to the NT server.



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: Newcomer Questions

[Jon Gardner]

on 8/9/2000 9:55 PM, Adrian Smith at [EMAIL PROTECTED] wrote:

> * DAT Tape drive - DDS3 or DDS4 attached to a PowerMac 7300, probably
> Sony (or LaCie which I think uses a Sony mechanism), no particular
> reason to go with Sony.
> * Retrospect 4.3 with clients on each of the Macs.

I'd start off with an Ecrix VXA drive instead...it'll easily hold all of
your data on one tape with room for the probable expansion you mentioned,
and it's cheaper than a DDS4.

<><
Jon L. Gardner '89, Computer Systems Manager 
Texas A&M University Dept. of Food Services 
Tel 979.458.1839 * Fax 979.845.2157 * Hip 979.229.4323
PGP public key available at 





--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Network communication failed - a hint

[Owen Watson]

I had a client that was showing up as "nothing in the container" and 
"network communication failed" when you went into the Remotes 
browser. I checked on the client, and what he'd done was put the 
whole hard disk as a private area (by mistake). I checked the docs, 
and a cursory glance didn't reveal this as a posible cause of the 
error messages. Over to you, Dantz!
-- 
.
Owen Watson
at home in Wellington, New Zealand


--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: Network communication failed - a hint

[Matthew Tevenan]

Hi Owen,

The "nothing in the container" error message would definitely be caused by
the user excluding all volumes. Not the 519, network communication failed,
though. I just quickly tested this with both an immediate and scripted
backup from both Retrospect 4.3 Mac and 5.11 Windows. No problems. Here's
basically all you should be seeing:

+Normal Backup using Untitled at 8/10/2000 1:01 PM
To backup set Backup Set DŠ

8/10/2000 1:01:26 PM: Connected to Matt/Toshiba
*Container Matt/Toshiba was empty (had no volumes)
8/10/2000 1:01:26 PM: Execution completed successfully
Quit at 8/10/2000 1:01 PM

Sorry, but there's something else going on here. Check out Dantz Tech Note
415 at



and if you can't resolve the 519 with the help of that, e-mail us at
[EMAIL PROTECTED]

Regards,

Matthew Tevenan
Technical Support Specialist
Dantz Development Corporation
925.253.3050 
[EMAIL PROTECTED]

> From: Owen Watson <[EMAIL PROTECTED]>
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Fri, 11 Aug 2000 07:55:55 +1200
> To: "retro-talk" <[EMAIL PROTECTED]>
> Subject: Network communication failed - a hint
> 
> I had a client that was showing up as "nothing in the container" and
> "network communication failed" when you went into the Remotes
> browser. I checked on the client, and what he'd done was put the
> whole hard disk as a private area (by mistake). I checked the docs,
> and a cursory glance didn't reveal this as a posible cause of the
> error messages. Over to you, Dantz!
> -- 
> .
> Owen Watson
> at home in Wellington, New Zealand
> 
> 
> --
> --
> To subscribe:[EMAIL PROTECTED]
> To unsubscribe:  [EMAIL PROTECTED]
> Archives:
> Problems?:   [EMAIL PROTECTED]
> 



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: freezes in Mac while backing up....

[Matt Barkdull]

Title: Re: freezes in Mac while backing
up


No solution here, but I have a similar problem on a G3
AppleShareIP server.  I followed Dantz's directions perfectly
and anytime I try to back the server up either locally or over the
network, the backup stops and the AppleShareIP server locks up.

I'm not running any special extensions beyond Apple OS 9.0.4 and
AppleShareIP.
I'm not backing up the mail directory at all, nor am I backing
up the System Folder.  I do those manually to CDR every couple
months.

If I shut down the mail server, it still locks up, if I shut
down the AppleShareIP server it works perfectly.  I've been
doing this manually since I cannot seem to figure out the problem
myself.


Hello, this
is my first posting to this mail list.
 
I have
recently purchased Retrospect Workgroup Backup 4.3 to backup a G3
server onto a Seagate Scorpion 24 (STD224000N-SB) tape drive, and I
have only one problem with it
The backup
run of any script ( or any backup attempt at all) will freeze at a
random point during execution, with the software running and the tape
drive read light off, and remain so forever.  If the system is
loaded without extensions, everything works fine, the script run
perfectly.
 
The obvious
problem I have been trying to fix is some sort of conflict with the
extensions, and I have been removing ones from the extensions folder
and disabling them to attempt to find the one or ones causing the
problem. This has not worked, and I am honestly
stumped.
 
Anyone have
any ideas?
 
 
-Andrew
Stein

Re: freezes in Mac while backing up....

[Matthew Tevenan]

Title: Re: freezes in Mac while backing up



Hi Matt,

Please call us so you can troubleshoot this with a tech. You may want to try the AppleShare lockout feature (available via the Options button of your script), but you may have something else unique to your system that may be causing this. 

It is important to note that if you're backing up an AppleShare server with AppleShare IP shut down, you are NOT getting any AppleShare privs. It's important to solve this as soon as possible, then, to make sure you can start backing up privs in the event of a disaster or disk failure. Please call.

Regards,

Matthew Tevenan
Technical Support Specialist
Dantz Development Corporation
925.253.3050 
[EMAIL PROTECTED] 

From: Matt Barkdull <[EMAIL PROTECTED]>
Reply-To: "retro-talk" <[EMAIL PROTECTED]>
Date: Thu, 10 Aug 2000 12:16:15 -0800
To: "retro-talk" <[EMAIL PROTECTED]>
Subject: Re: freezes in Mac while backing up


No solution here, but I have a similar problem on a G3 AppleShareIP server.  I followed Dantz's directions perfectly and anytime I try to back the server up either locally or over the network, the backup stops and the AppleShareIP server locks up.

I'm not running any special extensions beyond Apple OS 9.0.4 and AppleShareIP.
I'm not backing up the mail directory at all, nor am I backing up the System Folder.  I do those manually to CDR every couple months.

If I shut down the mail server, it still locks up, if I shut down the AppleShareIP server it works perfectly.  I've been doing this manually since I cannot seem to figure out the problem myself.


Hello, this is my first posting to this mail list.
 
I have recently purchased Retrospect Workgroup Backup 4.3 to backup a G3 server onto a Seagate Scorpion 24 (STD224000N-SB) tape drive, and I have only one problem with it
The backup run of any script ( or any backup attempt at all) will freeze at a random point during execution, with the software running and the tape drive read light off, and remain so forever.  If the system is loaded without extensions, everything works fine, the script run perfectly.
 
The obvious problem I have been trying to fix is some sort of conflict with the extensions, and I have been removing ones from the extensions folder and disabling them to attempt to find the one or ones causing the problem. This has not worked, and I am honestly stumped.
 
Anyone have any ideas?
 
 
-Andrew Stein

Re: freezes in Mac while backing up....

[Matthew Tevenan]

Title: Re: freezes in Mac while backing up



Andrew,

If this works with extensions off, you apparently have solved half the problem--extensions conflict. I'm not sure how you mean this has "not worked." It's extensions, you just have to figure out which ones. 

See the Retrospect 4.2 User's Guide, p. 209, under "Mac OS System Software Issues," for help with extensions troubleshooting. You could also consider a third-party package like Conflict Catcher, but the old-fashioned manual way should be adequate.

Of course, if you have questions, please call us.

Matthew Tevenan
Technical Support Specialist
Dantz Development Corporation
925.253.3050 
[EMAIL PROTECTED] 

From: Andrew Stein <[EMAIL PROTECTED]>
Reply-To: "retro-talk" <[EMAIL PROTECTED]>
Date: Thu, 10 Aug 2000 10:48:42 -0700
To: retro-talk <[EMAIL PROTECTED]>
Subject: freezes in Mac while backing up


Hello, this is my first posting to this mail list.
 
I have recently purchased Retrospect Workgroup Backup 4.3 to backup a G3 server onto a Seagate Scorpion 24 (STD224000N-SB) tape drive, and I have only one problem with it
The backup run of any script ( or any backup attempt at all) will freeze at a random point during execution, with the software running and the tape drive read light off, and remain so forever.  If the system is loaded without extensions, everything works fine, the script run perfectly. 
 
The obvious problem I have been trying to fix is some sort of conflict with the extensions, and I have been removing ones from the extensions folder and disabling them to attempt to find the one or ones causing the problem. This has not worked, and I am honestly stumped.
 
Anyone have any ideas?
 
 
-Andrew Stein

Re: NT Backup Failing

[Cory Rau]

Though I'm new to this list, I've been using many flavors of Retrospect for
a long time but have never encountered the problem I'm having now.

I've got Retrospect 5.11 installed on an NT Workstation machine (sp 6a) and
Retrospect client (most recent version downloaded from the Dantz web site
yesterday) on an NT Server (sp 5) file server (all Intel-based logic
boards).  We have a 10Base-T network which runs great in every respect.
I've been using this basic configuration for a long time but recently, the
parallel port on the machine running Retrospect took a dirt nap.  No
problem, I thought, I can install this HP Colorado Travan External 8MB
(parallel port connect) tape drive on another machine and just run the
backup from there.  Well, now, whenever we try to backup the NT Server,
Retrospect on the workstation freezes up at varying points in the backup.
Many times, I get a communication error (I believe it's -102). Other times,
Retrospect just hangs and the drive ceases all activity.  My only choice at
that point is to bring up the task manager and force the task to end.

I've updated all appropriate drivers and respective Retrospect products on
all machines and rebooted them all.  No go.

I realize that 'communication error' is supposed to indicate a disconnect
between the backup machine and the backup device but backups from a Mac
running Retrospect client to this same machine and drive succeeds just fine.
Admittedly, the backup on the Mac side is far smaller than the one on the NT
Server but still...

Anyone experienced this before?  I swear I have but I can't remember for the
life of me how we got it solved.  We've been running with this configuration
successfully for over a year.  All machines seem to be in tip-top shape.
The NT Server runs like a champ 24/7.

Thanks in advance for any help...I'm anxious to stop this file-transfer type
manual backup.

Regards,


| Cory Rau |
| Stimpson Co., Inc.   |
| 631-472-2000 x 306   |
| [EMAIL PROTECTED]|





--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: Strange behavior when restoring to entire disk

[Michael McLean]

on 8/4/00 5:07 PM, Michael Gaines at [EMAIL PROTECTED]
wrote:

> My question is why is Retrospect incorrectly reporting/calculating
> the space requirement of the data during the restore process? It
> appeared to correctly calculate the amount of data (~840MB) when I
> did a test backup of the newly restored partition.

I had a similar problem and it turns out that I had forgotten to format the
"new" drive with HFS+ and the different minimum file sizes were the problem.




--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: NT Backup Failing

[Matthew Tevenan]

Cory,

> I realize that 'communication error' is supposed to indicate a disconnect
> between the backup machine and the backup device but backups from a Mac
> running Retrospect client to this same machine and drive succeeds just fine.

That's basically what this error means, even if the drive works OK
elsewhere. Sounds like this PC/drive combination is having problems,
especially with the hanging problem. Off the top of my head:

Update SCSI card drivers.

Uninstall any extraneous drivers Windows or other software may have
installed.

Make sure ASPI is installed by running ASPICHK (installed into the
Retrospect Program Files directory).

Try a different tape in your drive.

Try the drive connected to a different PC with a different card.

If these don't help, please call us.

Matthew Tevenan
Technical Support Specialist
Dantz Development Corporation
925.253.3050 
[EMAIL PROTECTED]

> From: Cory Rau <[EMAIL PROTECTED]>
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Thu, 10 Aug 2000 17:51:00 -0400
> To: retro-talk <[EMAIL PROTECTED]>
> Subject: Re: NT Backup Failing
> 
> Though I'm new to this list, I've been using many flavors of Retrospect for
> a long time but have never encountered the problem I'm having now.
> 
> I've got Retrospect 5.11 installed on an NT Workstation machine (sp 6a) and
> Retrospect client (most recent version downloaded from the Dantz web site
> yesterday) on an NT Server (sp 5) file server (all Intel-based logic
> boards).  We have a 10Base-T network which runs great in every respect.
> I've been using this basic configuration for a long time but recently, the
> parallel port on the machine running Retrospect took a dirt nap.  No
> problem, I thought, I can install this HP Colorado Travan External 8MB
> (parallel port connect) tape drive on another machine and just run the
> backup from there.  Well, now, whenever we try to backup the NT Server,
> Retrospect on the workstation freezes up at varying points in the backup.
> Many times, I get a communication error (I believe it's -102). Other times,
> Retrospect just hangs and the drive ceases all activity.  My only choice at
> that point is to bring up the task manager and force the task to end.
> 
> I've updated all appropriate drivers and respective Retrospect products on
> all machines and rebooted them all.  No go.
> 
> I realize that 'communication error' is supposed to indicate a disconnect
> between the backup machine and the backup device but backups from a Mac
> running Retrospect client to this same machine and drive succeeds just fine.
> Admittedly, the backup on the Mac side is far smaller than the one on the NT
> Server but still...
> 
> Anyone experienced this before?  I swear I have but I can't remember for the
> life of me how we got it solved.  We've been running with this configuration
> successfully for over a year.  All machines seem to be in tip-top shape.
> The NT Server runs like a champ 24/7.
> 
> Thanks in advance for any help...I'm anxious to stop this file-transfer type
> manual backup.
> 
> Regards,
> 
> 
> | Cory Rau |
> | Stimpson Co., Inc.   |
> | 631-472-2000 x 306   |
> | [EMAIL PROTECTED]|
> 
> 
> 
> 
> 
> --
> --
> To subscribe:[EMAIL PROTECTED]
> To unsubscribe:  [EMAIL PROTECTED]
> Archives:
> Problems?:   [EMAIL PROTECTED]
> 



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Another new guys

[Francois Pepin]

Hopefully those questions won't be all too out of the way for now, please
tell tell if that's the case.

Has anyone had any experience with the Onstream tapes? I managed to convince
the people that we needed a backup system, and they're rather get a less
expensive drive. I know it's not always the brightest idea to try to save a
few bucks where backups are concerned, but I'd like to have more information
on there.

Did anyone ever created an applescript or something (we're on Macs here) to
receive mails about the status of the backups? That would make
administration a bit easier for us if it could do that, but I couldn't see
it in the documentation.

Also, is there any advantage of doing backups through an AppleTalk network
rather than a TCP/IP one, since the latter is usually faster?

Thanks for your help,

Francois Pepin




--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: Network communication failed - a hint

[Owen Watson]

The "network communication failed" message was seen in the network
browser Retro 4.3 Mac, when i went to configure the remote: the first
two panes were OK, but the last one (Volumes) failed with the
aforesaid error message.

Thanks for the other info: the Tech Note was useful.


>Hi Owen,
>
>The "nothing in the container" error message would definitely be caused by
>the user excluding all volumes. Not the 519, network communication failed,
>though. I just quickly tested this with both an immediate and scripted
>backup from both Retrospect 4.3 Mac and 5.11 Windows. No problems. Here's
>basically all you should be seeing:
>
>+Normal Backup using Untitled at 8/10/2000 1:01 PM
> To backup set Backup Set DŠ
>
> 8/10/2000 1:01:26 PM: Connected to Matt/Toshiba
>*Container Matt/Toshiba was empty (had no volumes)
> 8/10/2000 1:01:26 PM: Execution completed successfully
> Quit at 8/10/2000 1:01 PM
>
>Sorry, but there's something else going on here. Check out Dantz Tech Note
>415 at
>
>
>
>and if you can't resolve the 519 with the help of that, e-mail us at
>[EMAIL PROTECTED]
>
>Regards,
>
>Matthew Tevenan
>Technical Support Specialist
>Dantz Development Corporation
>925.253.3050
>[EMAIL PROTECTED]
--
.
Owen Watson
at home in Wellington, New Zealand


--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]