Re: Scripting within Retrospect.

2000-07-28 Thread Matthew Tevenan 

The AppleShare lockout feature only works when Retrospect is running on the
AppleShare server. It will not lock out users when backing up AppleShare
servers remotely.

Regards,

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

> From: casper <[EMAIL PROTECTED]>
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Thu, 27 Jul 2000 17:02:43 -0400
> To: retro-talk <[EMAIL PROTECTED]>
> Subject: Re: Scripting within Retrospect.
> 
> Thank you for the advice.
> 
> I have another question however. I assume that Appleshare lockout works with
> the appleshare clients. Is this functionality still realized using Mac
> Manager? We have another small site that is interested in automating their
> backup procedure.
> 
> Thanks again.
> 
> 
>> The "if it ain't broke don't fix it" saying definitely applies in this case.
>> Retrospect is completely compatible with AppleShare. It's just when you have
>> a server that's being slammed and a Retrospect backup happening at the same
>> time that things can get dicey. If this is working for you, don't change it.
>> 
>> Also, one more thing. The AppleShare lockout feature is NOT the same thing
>> as shutting down AppleShare. The AppleShare lockout feature (accessible in
>> the Options of your backup script) automatically logs out users before local
>> server volume backups. AppleShare is still running. Something extremely
>> important to note is that to get a good backup of your AppleShare server,
>> AppleShare MUST be running. Otherwise you will not be backing up the access
>> privileges.
>> 
>> Feel free to call us should you have any other questions.
>> 
>> Regards,
>> 
>> Matthew Tevenan
>> Technical Support Specialist
>> Dantz Development Corporation
>> 925.253.3050 
>> [EMAIL PROTECTED]
> 
> 
> 
> --
> --
> To subscribe:[EMAIL PROTECTED]
> To unsubscribe:  [EMAIL PROTECTED]
> Archives:<http://list.working-dogs.com/lists/retro-talk/>
> Problems?:   [EMAIL PROTECTED]
> 



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:<http://list.working-dogs.com/lists/retro-talk/>
Problems?:   [EMAIL PROTECTED]

Re: Scripting within Retrospect.

2000-07-27 Thread casper 

Thank you for the advice.

I have another question however. I assume that Appleshare lockout works with
the appleshare clients. Is this functionality still realized using Mac
Manager? We have another small site that is interested in automating their
backup procedure.

Thanks again.


> The "if it ain't broke don't fix it" saying definitely applies in this case.
> Retrospect is completely compatible with AppleShare. It's just when you have
> a server that's being slammed and a Retrospect backup happening at the same
> time that things can get dicey. If this is working for you, don't change it.
> 
> Also, one more thing. The AppleShare lockout feature is NOT the same thing
> as shutting down AppleShare. The AppleShare lockout feature (accessible in
> the Options of your backup script) automatically logs out users before local
> server volume backups. AppleShare is still running. Something extremely
> important to note is that to get a good backup of your AppleShare server,
> AppleShare MUST be running. Otherwise you will not be backing up the access
> privileges.
> 
> Feel free to call us should you have any other questions.
> 
> Regards,
> 
> Matthew Tevenan
> Technical Support Specialist
> Dantz Development Corporation
> 925.253.3050 
> [EMAIL PROTECTED]



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

Re: Scripting within Retrospect.

2000-07-27 Thread Chris Benjamin 

on 7/27/00 11:32 AM, Matthew Tevenan at [EMAIL PROTECTED] wrote:

> The AppleShare lockout feature (accessible in
> the Options of your backup script) automatically logs out users before local
> server volume backups.

Matthew,

Thank you for bringing up the AppleShare lockout feature. I failed to
mention it in my reply. I am using this feature just in case there happens
to be someone working late here at the studio. I run a digital photography
studio and unfortunately the nature of the beast is that sometimes we find
ourselves working late in order to meet a deadline. With the AppleShare
lockout feature in place, it allows anyone working off the servers to either
save their work and log out or to suspend the backup script until finished
and then running the backup manually before leaving for the night. Thanks
again for mentioning it, as it is very relative and also a great feature of
Retrospect to be aware of.

Chris

-

Christopher M. Benjamin
A Trice Digital
114-C Dekalb Street
Bridgeport, PA 19405
610-272-6900 (Voice)
610-272-8600 (Fax)

[EMAIL PROTECTED]

http://www.atricedigital.com

http://www.atricephoto.com






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

Re: Scripting within Retrospect.

2000-07-27 Thread Matthew Tevenan 

Chris,

The "if it ain't broke don't fix it" saying definitely applies in this case.
Retrospect is completely compatible with AppleShare. It's just when you have
a server that's being slammed and a Retrospect backup happening at the same
time that things can get dicey. If this is working for you, don't change it.

Also, one more thing. The AppleShare lockout feature is NOT the same thing
as shutting down AppleShare. The AppleShare lockout feature (accessible in
the Options of your backup script) automatically logs out users before local
server volume backups. AppleShare is still running. Something extremely
important to note is that to get a good backup of your AppleShare server,
AppleShare MUST be running. Otherwise you will not be backing up the access
privileges.

Feel free to call us should you have any other questions.

Regards,

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

> From: Chris Benjamin <[EMAIL PROTECTED]>
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Thu, 27 Jul 2000 11:17:54 -0400
> To: retro-talk <[EMAIL PROTECTED]>
> Subject: Re: Scripting within Retrospect.
> 
> on 7/26/00 4:38 PM, Jaeger, Luke at [EMAIL PROTECTED] wrote:
> 
>> you should run Retrospect on a different machine and have the
>> ASIP server be logged in as a client. It sounds wrong, but it really works
>> better for all kinds of reasons.
> 
> I'm curious as to what "all of the better reasons" Mr. Jaeger is referring
> to. My current configuration is almost identical to the one that Jason has
> and I've been running my backups to a DLT drive which is DIRECTLY connected
> to my ASIP server. Since beginning this scenario over six months ago, I have
> had absolutely no problems what so ever. When I first decided to move up to
> the DLT drive, I also wanted to try to improve my backup speed and
> stability. This need prompted the thought of a direct connection to the
> server as opposed accessing as a client. After talking to a few fellow
> colleagues who also had the same concerns, the general consensus  was to
> hook-up the DLT directly to the server to increase the overall performance
> during the actual backup. I've set the backup time late enough in the day so
> that for 95% of the time there isn't anyone in the studio who would be
> actually hitting the server during the backup. This eliminates the chance of
> interrupting the backup. There has never been a need to shutdown the ASIP
> services.
> 
> I'm sure that I'm like most people who believe that if you have a system or
> workflow that's been reliable for you, why bother toying around with it.
> It's kind of like the old saying, "If it's not broken, don't fix it!".
> However, I also strongly believe in the idea of building a better mouse
> trap, especially if the end result is a faster, better, and more stable work
> environment. Therefore, I look forward to discussing further any ideas
> and/or theories that Mr. Jaeger or anyone else on list has to offer on the
> subject. Anyone at Dantz Tech Support have any thoughts?
> 
> Best Regards,
> 
> Chris
> A Trice Digital
> 
> -
> 
> Christopher M. Benjamin
> A Trice Digital
> 114-C Dekalb Street
> Bridgeport, PA 19405
> 610-272-6900 (Voice)
> 610-272-8600 (Fax)
> 
> [EMAIL PROTECTED]
> 
> http://www.atricedigital.com
> 
> http://www.atricephoto.com
> 
> 
> 
> 
> 
> 
> --
> --
> To subscribe:[EMAIL PROTECTED]
> To unsubscribe:  [EMAIL PROTECTED]
> Archives:<http://list.working-dogs.com/lists/retro-talk/>
> Problems?:   [EMAIL PROTECTED]
> 



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:<http://list.working-dogs.com/lists/retro-talk/>
Problems?:   [EMAIL PROTECTED]

Re: Scripting within Retrospect.

2000-07-27 Thread Chris Benjamin 

on 7/26/00 4:38 PM, Jaeger, Luke at [EMAIL PROTECTED] wrote:

> you should run Retrospect on a different machine and have the
> ASIP server be logged in as a client. It sounds wrong, but it really works
> better for all kinds of reasons.

I'm curious as to what "all of the better reasons" Mr. Jaeger is referring
to. My current configuration is almost identical to the one that Jason has
and I've been running my backups to a DLT drive which is DIRECTLY connected
to my ASIP server. Since beginning this scenario over six months ago, I have
had absolutely no problems what so ever. When I first decided to move up to
the DLT drive, I also wanted to try to improve my backup speed and
stability. This need prompted the thought of a direct connection to the
server as opposed accessing as a client. After talking to a few fellow
colleagues who also had the same concerns, the general consensus  was to
hook-up the DLT directly to the server to increase the overall performance
during the actual backup. I've set the backup time late enough in the day so
that for 95% of the time there isn't anyone in the studio who would be
actually hitting the server during the backup. This eliminates the chance of
interrupting the backup. There has never been a need to shutdown the ASIP
services.

I'm sure that I'm like most people who believe that if you have a system or
workflow that's been reliable for you, why bother toying around with it.
It's kind of like the old saying, "If it's not broken, don't fix it!".
However, I also strongly believe in the idea of building a better mouse
trap, especially if the end result is a faster, better, and more stable work
environment. Therefore, I look forward to discussing further any ideas
and/or theories that Mr. Jaeger or anyone else on list has to offer on the
subject. Anyone at Dantz Tech Support have any thoughts?

Best Regards,

Chris
A Trice Digital

-

Christopher M. Benjamin
A Trice Digital
114-C Dekalb Street
Bridgeport, PA 19405
610-272-6900 (Voice)
610-272-8600 (Fax)

[EMAIL PROTECTED]

http://www.atricedigital.com

http://www.atricephoto.com






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

Re: Scripting within Retrospect.

2000-07-26 Thread John Gee 

>I'm seeking a little advice and maybe a little help. I'm new to Retrospect
>and am looking for a way to automate more of my backup procedure. I'd like
>to utilize Retrospect's automatic execution features to do the following.

[...]

>Is this possible? Does anyone have any ideas or sample scripts?

The AppleScript Utilities folder in your Retrospect folder has some 
example scripts which will get you started if you are familiar with 
AppleScript.
-- 
John Gee[EMAIL PROTECTED]
Dunedin, New ZealandProgrammers live in interesting times...



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

RE: Scripting within Retrospect.

2000-07-26 Thread Jaeger, Luke 

If possible, you should run Retrospect on a different machine and have the
ASIP server be logged in as a client. It sounds wrong, but it really works
better for all kinds of reasons. (Including eliminating the need for you to
quit all your services every night).



top of the world,

Luke Jaeger, Technology Coordinator
Disney Magazine Publishing
Northampton, Massachusetts
[EMAIL PROTECTED]

Any opinions expressed in this message are my own and may not represent the
opinions of Disney Publishing, etc etc etc.

*

> --
> From: casper
> Reply To: retro-talk
> Sent: Wednesday, July 26, 2000 4:33 PM
> To:   [EMAIL PROTECTED]
> Subject:  Scripting within Retrospect.
> 
> I'm seeking a little advice and maybe a little help. I'm new to Retrospect
> and am looking for a way to automate more of my backup procedure. I'd like
> to utilize Retrospect's automatic execution features to do the following.
> 
> Turn of File/Web services
> Turn of Mail services
> Quit AppleShareIP
> Quit Powerchute
> Run a specified Retrospect script
> Turn on the above services
> 
> Is this possible? Does anyone have any ideas or sample scripts?
> 
> The following is running:
> 
> ASIP 6.3.1
> Mac OS 9.0.4
> Retrospect 4.2
> Powerchute 2.0.3
> 
> Any help would be greatly appreciated.
> 
> Jason Pruss
> Advantage Consulting and Technologies
> 
> 
> 
> --
> --
> To subscribe:[EMAIL PROTECTED]
> To unsubscribe:  [EMAIL PROTECTED]
> Archives:<http://list.working-dogs.com/lists/retro-talk/>
> Problems?:   [EMAIL PROTECTED]
> 
> 


--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:<http://list.working-dogs.com/lists/retro-talk/>
Problems?:   [EMAIL PROTECTED]

Scripting within Retrospect.

2000-07-26 Thread casper 

I'm seeking a little advice and maybe a little help. I'm new to Retrospect
and am looking for a way to automate more of my backup procedure. I'd like
to utilize Retrospect's automatic execution features to do the following.

Turn of File/Web services
Turn of Mail services
Quit AppleShareIP
Quit Powerchute
Run a specified Retrospect script
Turn on the above services

Is this possible? Does anyone have any ideas or sample scripts?

The following is running:

ASIP 6.3.1
Mac OS 9.0.4
Retrospect 4.2
Powerchute 2.0.3

Any help would be greatly appreciated.

Jason Pruss
Advantage Consulting and Technologies



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