Jump to content

Search the Community

Showing results for tags 'script'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 11 results

  1. I'm looking at Image 1 and I'm confused why the Script 7 Day seems to think it needs to do schedules in the past ... I look at the Script (Images 2 and 3) and it looks right to me.
  2. I sometimes find that I can't change a script. In this case, I had a script that was set up to copy the latest backups from my "old" set to the cumulative "2015" set. The schedule is to do this once every three months for archive purposes. The old script had the "2014" destination set, and all I wanted to do was change the destination to the "2015" set. I would open the script, click the new destination, set the schedule, and hit "save". It would revert to the old destination set. I tried this a bunch of times. It turns out that the schedule is irrelevant. I click on the new destination, hit save, and the destination reverts back. I tried stopping and re-starting both the console and the engine, and made sure nothing was running. I tried deleting and re-creating the destination media set (empty, as of today). The only thing I found that would allow me to change this script was to delete the script, and then re-add the script. THEN it would let me set the destination as I wished. I smell a bug, although I don't know how to reproduce it. I've seen this before, but I can't pick out the pattern (yet!)
  3. I had a couple of old scripts where the source and destinations had been deleted. I tried to copy and modify one of them, to add source and destination to use it. What I saw was really odd. The number of available backups for restore ops should be large (50+?). I saw 7. I looked at other restore scripts, and they all seemed to show just the same 7 restore options. (2 screenshots attached) I then tried to delete the script. The "really delete" dialog came up, but the script would not go away. I tried several times. I restarted the console, and the backups reappeared, and the scripts could be deleted. Bug. Not sure if I could reproduce it.
  4. (Retro 10.2.0 (201) on Mac OS X 10.8.4, Mac Mini 16 GB mem) I have had several incidents where I have duplicated a script while it was running, presuming that the script would be copied, and i could tweak the duplicate without disturbing the original, running script. I have stopped doing this because it seems to screw up the original script in strange ways. Thinking about what I have seen, though, I think I know what's happening. The "duplicate" button does indeed duplicate the script, but names the original as "copy", which leads me to modify the original, and leave the copy unchanged. I have seen errors in the logs, backups written to the wrong media set, and other strange happenings. This most recent incident would be fully explained by this scenario. I encourage the folks at Retro to try this on a long-running script. I bet I'm right. BTW - changing a running script should either be disallowed, or fixed so the running script cannot be screwed up, or at least a warning would be nice.... Thanks,
  5. I think the status displays are confusing for scripted verification in this version of Retrospect. In 10.5.0 the Detail and List view windows show: Summary shows a source and destination that don't make sense - a source and a destination in a verify? Details in the script accurately show multiple execution schedules for DIFFERENT sources List View shows source and destinations. On a Verify? Destination might be the catalog file, but this simply doesn't make sense.
  6. I have a script to copy most recent backups to an external hard drive. There exists a media set for the drive, with one member: the external drive. The script is supposed to recycle the external drive media set before beginning the copy, with my intention being that the external drive holds a complete up to date copy of all backup sources, without older versions of files taking up space. When the script runs, it goes straight to "Matching" and then "Copying", with no recycle process. Note: below it indicates the option "Match source Media Set to Destination Media Set" is checked; I have just tried running the script with this option unchecked, and it exhibits the same behavior. Old backups are still on the drive while new files are being created. Essentially, Retrospect doesn't appear to be respecting the "Media action: Recycle Media Set" setting. Is the problem that this is a disk media set, rather than tape drive? The script is set up as follows: Summary Status: Scheduled Type: Copy Backup Rule: All files Options: Data compression off Backups (my main media set) Media sets (the External Drive Media Set) The Schedule detail shows the recycle icon Sources Copy most recent backups for each source Main Media Set selected Destinations External Drive Media Set selected Rules All Files Schedule Destination: External Drive selected. Media Action: Recycle Media Set Start: 11PM Repeat: Weekly Every [1] week on [Friday] Stop: when done Options Copy Backup Media Verification checked Match source Media Set to Destination Media Set checked Don't add duplicates to the Media Set checked
  7. I recently created a script (Retro 10.2) to verify my media sets periodically. It has a bunch of media sets to do. When I set up a schedule, I note that there is a popup listing all 8 media sets to be verified. When I set up a schedule, I can "attach" that schedule to one of the media sets. If I have multiple schedules, they can be "attached" to different sets. Which set seems to make no difference. Happily, any schedule, attached to any set verifies all 8 sets. What is the purpose and significance of the popup?
  8. I change my backup data sets either monthly or quarterly. I have seven different backup sets, and for each backup set, I need to manually remove the "old" backup set name, and insert the "new" backup set name. Are there any tools, even from third parties, that could automate this process? Ideally such a tool would also create the new backup sets also. Thanks.
  9. The "disable all schedules" button in the "Schedule" pane of a script allows me to check it, and disable its scheduled execution without honoring the "save" rules. I consider this a bug. No changes should be "saved" to any script unless I click "save". If there *must* be a difference with one element of the script, it should be highlighted somehow as not subject to the normal rules. The "save" button was a big improvement, in my opinion. This is a flaw.
  10. I apologize if I am repeating a previously asked question. I am using Retrospect 10.0.1 on a MacBook Pro (OS X 10.8.2). Is it possible for a Retrospect backup script to run an Applescript or a Unix shell script programatically at the completion of the backup script? Alternatively, how can I tell programatically when a Retrospect backup script has completed execution? Is there some signal that could be monitored by an Applescript or a Unix shell script that would indicate completion of the backup script? I ask because I run a backup script every day at 3AM and would like to do some non-Retrospect cleanup tasks at the completion of each backup.
  11. I just had one of my proactive scripts quit because it hit its "scheduled stop time". I wanted it to finish, so rather than create a new script, I thought I would add another schedule item to run it just for today, leaving the existing schedule and script intact. When I went to add another script entry for "10 AM to 3 PM/every day", I ended up with two schedule entries on the script, both saying "12AM-12AM/every day". Clearly the act of adding the additional script entry overwrote/corrupted the existing schedule entry. I have seen this before in other circumstances. In my experience, the scheduling machinery does not work well. A single entry generally works, but more than one is trouble. (Retro 9.0.2.107, Mac OS X 10.6.8)
×