Jump to content

jotrago

Members
  • Content count

    146
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by jotrago

  1. jotrago

    Restart Verify job

    At the simplest level if you deprive the verify job of the tapes it needs it will just stop in "Awaiting Media" mode. So you could set it going, then during your backup window ensure that only your backup tapes are available, when the backup finishes replace the verify tapes. If your library has cartridges which hold batches of tapes the above process may be mecahnically fairly simple. With a 40 Tape backupset I guess you have a tape library or autochanger of some sort, and possibly the "Advanced Tape Support" license to use multiple drives. Can you give us details of your setup, What version of Retrospect, MultiServer/Server/Pro and which release and platform. What backup devices you have, eg how many drives / slots etc. If you have multiple drives you may be able to bind a drive to the verify job, and use the other(s) for backups. There is a "Binding" Tab on the Storage Devices Window that allows youmanually allocate Drives to Backup sets. See the Manual Ch7 Controlling Operations > Multiple Concurrent Executions > Mutiple Drives > Binding tape Backup Sets to Tape Drives Verify Jobs have an option to only verify "Unverified" backupsets, so you can run the same job and it will find anything that needs verifying, ignoring anything already verified. See Manual Ch11 Tools > Maintenance & Repair > Verifying Backup Media
  2. The secret is to have a backup copy of the Catalogs from DC2 on DC1 Set up a Duplicate job on DC2 to Duplicate your Catalogs Folder to a Share on DC1 (And Vice Versa) Time it to run just after all your backups to the RD device have finished so you get the latest data. When you need to recover DC2 RD Disk on DC1 find the DC2 Catalog files and drag and drop them onto the Retro Window Retro Will recognise the backup sets and you should be able recover from there. See my post here for more details http://forums.retrospect.com/index.php?/topic/151293-best-way-to-backup-a-server/
  3. Could be. The old Retro 6 PPC client for Mac is still available here http://download.retrospect.com/archives/client_osx-6_3_029.dmg I am running it on a Mac G5 with 10.4 Tiger backing up to a Retro 9.5 Windows Server Give it a go
  4. jotrago

    COM+ REGDB errors during backup

    Hi, Running single server I suspect you do not have the Open File Add On. File "C:\Windows\SysWOW64\log.txt": can't read, error -1020 ( sharing violation) is a system log file which is probably open by windows all the time, and thus Retro cannot back it up. So you have two choices, 1. Get the Open File add On or 2. Exclude the files from backup by adding them to a selector. See my post on selectors for more insight http://forums.retrospect.com/index.php?/topic/151365-how-to-nesting-selectors/ In my experience there are usually quite a few of these system files which are always open and can never be backed up on a running system Inspecting them carefully will reveal most of them are either log files, or temp files, and they can be excluded. This keeps your Backup logs clean so you do not get used to having dozens of errors and ignoring them. Eventually you will ignore an important error and suffer the consequenc es. I always strive to have a normal backup run without any errors in the Backup log. Incidentally, Block level backup by default is only invoked for files over 100MB so either this is a very big log, or maybe you have lowered the BLI threshold.
  5. jotrago

    How To Upgrade v7.6 to v9.5 For Windows

    Hi Cecil 1. Yes 9.5 is supported on XP See the Users Guide > Getting Started here http://www.retrospect.com/en/documentation/user_guide/win/getting_started#50458635_67854 It pretty much addresses all your questions. You can also download a copy here for offline study. http://www.retrospect.com/en/documentation/user_guide/win.pdf 2. You can Run the installer over your existing installation, instructions are on the same page as above. That said it never hurts to take a backup. especially your catalogs, and configs. See the 7.5 User guide > Management > Moving Retrospect, & Catalog & configuration Backups for tips on doing this. 3. Upgrading the Clients would definitely be a good idea, there are significant changes with the 9.5 client. 4. Hey if ain't broke, don't fix it! Some of the newer features rely on features of later OS releases and may not work with XP. Note that an upgrade from 7.x to 9.x would be chargeable unless you have kept up with your Annual Support and maintenance. Check you current license for available upgrades here http://www.retrospect.com/en/products/upgrade Good Luck
  6. I have spent some time getting my head around this and it can be fun. I wrote myself a How To which I have just posted here http://forums.retrospect.com/index.php?/topic/151365-how-to-nesting-selectors/ I hope that will help you. Selectors are extremely useful and powerful, and it is well worth the effort to understand them. Cheers
  7. Nesting Selectors Retrospect Selectors have sections to INCLUDE and EXCLUDE specified items EXCLUDES always take priority over INCLUDES You can use another selector in a selector item definition. Doing this presents some subtleties. Some experimentation suggest that it works like this:- Selectors intended for inclusion in other selectors should only specify INCLUDES OR EXCLUDES but not both {it gets too mind bending otherwise} THUS:- Selectors specified in the EXCLUDE section of the parent MUST specify the files to be INCLUDED {in the exclude}. Similarly, Selectors specified in the INCLUDE section of the parent MUST specify the files to be INCLUDED {in the include} This behaviour CAN be reversed by using the IS NOT operator when specifying the Child Selector but this also starts to get mind bending Put another way if you include a selector which says EXCLUDE something, in an EXCLUDE section then those items will be EXCLUDED from the EXCLUDE and will be INCLUDED in the backup. THUS it appears one can apply traditional mathematical sign rules to nesting Selectors INCLUDE + INCLUDE = INCLUDE EXCLUDE + INCLUDE = EXCLUDE INCLUDE + EXCLUDE = EXCLUDE EXCLUDE + EXCLUDE = INCLUDE !!!! It pays to use the TEST facility. While EDITING a selector hit the BLUE TICK button and select a suitable volume or subvolume to try out your rule. So in sites with more complex Selector Requirements I use the following approach. Create Selectors Named for the types of files, and ONLY specify items in the INCLUDE section EG:- 5-Xco-Server Temp; include tmp Temp etc etc EG:- 5-Xco-Music; include *.mp3, m:\Artists etc etc. Then Create a selector named for the Script or Function it refers to EG: 1- Xco-Servers. This Selector will only ever reference other selectors. EG add EG 5-Xco-Server Temp to the EXCLUDE Section, and add EG 5-Xco-Music to the INCLUDE Section You can then create many selectors for various files, types etc, and simply add them to your Script Selectors. Using a good naming convention results in a very readable list of Selectors which indicates quite intuitively what they are doing. Preceding ALL your custom selectors with a standard character or two ensures they are grouped together in the list and not confused with the standard Retro Selectors. (I use "Digit-Company or Site abbreviation-Description" which allows me to order & group logically. I have found it best to NOT change the default selectors, rather Duplicate and Rename them, thus you always have the originals to refer to as examples and use as templates. Happy Selecting
  8. Yes LTO is very reliable technology, and yes Reading back a tape is time consuming. In the end it is your choice. Balancing time savings against assurance of successful copy. If your source tapes will still be available in the future should one of your LTO5s turn out to be unreadable, then you could probably take a chance and skip the verify. But if the source tapes will be retired or disposed of, leaving your LTO5s as the ONLY copy of your data, then I would do the MD5 Verification, just to be sure. Good Luck
  9. Verification has nothing to do with the Type, Size, or Number of files being backed up. It's purpose is to verify whether the data that has been backed up or transferred to the target BackupSet has been done exactly and without error and to ensure the the target BackupSet is readable for a restore or recovery. The decision on whether and how to verify depends on how sure you want to be that you have a good copy of your data. It sounds like you may be Transferring Backupsets from older LTOx tapes to newer LTO5 tapes, perhaps you have a new Tape Drive or Library and are moving all your data with a view to retiring the old LTO. In this case you may rely on the built in, Read After Write Verification feature of the LTO drive itself. However if you will be retiring the original tapes you will definitely want to be sure your copies are good. I would then recommend you perform a MD5 verification to be sure that the new target tapes are readable.
  10. There's also a discussion here http://forums.retrospect.com/index.php?/topic/150217-lto-verification/
  11. It's an alternative method to verify that your backup data is good. It reads all the data back from a backupset and compares it with an MD5 checksum. With LTO Drives Verification is not really necessary, their Read heads are physically positioned after the Write head and the drive internally reads the data back after the write and checks it against the original data while it is still in the memory buffer. Having Retrospect perform additional verification just increases tape and drive wear. See a nice animation here http://lto.org/technology/primer3.html If you are transferring backupsets or snapshots, from one tape backupset to another, then if they complete successfully you have verified the source tapes by definition. However for backup to disk you need to do some form of verification. Full Verification reads ALL the data back from the Backupset, AND the Source data, and compares and verifies it. This has a performance impact on the source system while verification is taking place. An alternative is to use the MD5 Verification. During Backup Retrospect calculates MD5 checksums on the source data and stores them in the Catalog. After the backup the data can be read back from the Backupset, and compared with the MD5 checksum WITHOUT re-reading the source data, thus relieving the strain on the source system. AND you can schedule these verifications as separate Jobs (Backup > Verification) or set the flag on your backup job to have them done immediately after. I like using separate jobs, as these can be run during the day since they don't affect source systems, which saves a lot of time during your backup window, AND there is an option to only verify data not already verified. So you can run a job against a whole backupset, and only the newest data is verified. Check the user guide for Verification - Backup Script Preferences - Scripted Verification - Execution Options > Verification
  12. jotrago

    Spectra 2K tape library not detected by 7.6.111

    You might check for Updates. Retro may have an updated driver package or other updates. Help > Retrospect Updates Also check the Compatibility lists on the Retro WebSite. http://retrospect.com/en/devices I am not sure I entirely agree with Lennart, In my experience the devices need to be recognised by Windows and show up in Device manager. Typically the Drive will be correctly recognised by name because windows has built in drivers for most tape drives. the Library / Autochanger may show up as "Unknown Medium Changer" in earlier Windows <= 2003 or by name in later versions which do have built in support for some Libraries. Windows Removable Storage manager usually wants to take control of any tape drives and libraries it finds, hence disabling it to prevent contention. If Retro Still does not recognise the devices, try loading the latest appropriate windows drivers from the Manufacturers (often they are newer than the built in windows drivers.)
  13. You can Restart Retro in your session by clicking the green "power" button in that little Retro window. It may take some time, especially if Retro is busy with a backup, as it will first gracefully stop what it is doing. I also find this aspect of Retrospect confusing and annoying, especially if you use RDP to remotely access the server, as everyone does these days. Retrospect runs as a normal windows application (like Excel or whatever) and not as a service (like most other backup applications) This means it has to run as some user. You can control which user, or leave the "System" account in the config settings. You can also control when and how Retro closes or stays running. If you are controlling Retro almost exclusively through RDP then check the manual for "Terminal Services" there is a section there discussing this. Unfortunately it is difficult to retrofit the solution as it involves actually installing Retro through Terminal Services.
  14. jotrago

    Spectra 2K tape library not detected by 7.6.111

    If that doesn't do it you might consider these tips 1. if you are not using Windows Removable Storage Manager Service to share the library between multiple applications, disable the service altogether 2. I see that the Tape drive has a lower SCSI ID than the Library itself. Sometimes systems prefer to see the library first. On most Libraries you can change the SCSI ID's of the changer and / or the drive. Set the Changer to 2.0.0 and the drive to 2.1.0 or at least make the drive a higher ID than the library. You should find the SCSI settings buried in the Device Configuration in the library somewhere.
  15. jotrago

    Best way to backup a server

    Make sure to check the System State backup in the Script Options. Consider setting up the Bare Metal Disaster Recovery Facilities and test them Consider creating separate duplication jobs for your config file and catalogs, so they are available as normal files (not a backup set) in the event of a Disaster. See the User Guide > CH10 Management > Catalog & Config backups and User Guide > CH10 Management > Moving Retrospect. The same technique applies to a bare metal recovery of the Retro Server
  16. The new Dashboard in later versions of Retrospect Gives a summary table of the Backup sets with their total size and size used. Depending on how you've organised your Backupsets this may be useful.
  17. Could be, I've used Retro 7, extensively in the past and seem to remember using this technique. Currently I am on 9. Here's an example of 3 scripts scheduled at 1 minute intervals using the same execution unit #4 I rigged the names so we can see whether they run in scheduled or alpha order. https://app.box.com/s/y6du7m7fnm9v1al1wkb3 Here is the first task running in exec4 https://app.box.com/s/qig2o5imiudi7lmvo4ix here are the other two waiting in order, If it is Alpha order then the transfer should run before the verify https://app.box.com/s/4c74r2vxbcrsngqo86g1 The key here is the Status, we can see the the Transfer Task is waiting for the Verify task. I think if the status indicates a task is waiting for another task, then that is due to them being allocated to the same Exec Unit. So the Backup Ran, Then the verify Then the Transfer Each immediately after the previous one finished.
  18. The manual mentions that if you simply submit a whole bunch of scripts, or "Run Documents", then they run in alphabetical order, but I have never used that method. I do regularly use the method described above. I assume that by submitting them with a schedule in a specific order, forces that order on them. I like to do my verification during the day, as a separate task after the backups have run overnight (saves on Backup time), this is typically followed by a snapshot transfer to generate offsite copies to tape or removable disk, which is then followed by Catalog, Logs, & Config Duplication jobs for DR copies. I typically set all these up using the above technique, to ensure they run in the correct sequence but in the shortest time. Works for me.
  19. This is true. And that is why this is posted in the Server, SBS, & Multiserver forum
  20. jotrago

    Ubuntu LTS 14.04 64-bit Install

    Awesome, Can't Wait!
  21. jotrago

    Proper Linux GUI + backup client

    Yes Please!. Gui Client for Desktop Ubuntu 64 bit & derivatives
  22. Here's another way to get tasks to run sequentially as quickly as possible http://forums.retrospect.com/index.php?/topic/151254-how-to-run-tasks-sequentially-as-quickly-as-possible.
  23. jotrago

    Impact of "Forget Client"

    To avoid losing data when recycling media sets, but still keep a backup, you could Transfer the most recent (or any other) Snapshots of your DeCom clients to another backupset. If you have many backups of them over a lengthy period this could save considerable space on your backup media.
  24. jotrago

    Impact of "Forget Client"

    OR You could create a folder for "Decommissioned Clients" and drag them in there. Then you still have them but they are separated from your production clients.
  25. You did set the dates to ALL ?? Also a snapshot occurs every time the backup runs, even when there is nothing to backup. The Sessions will show you what was actually backed on any occasion. Do the dates correlate any better with Sessions. Try changing the "Show > Most Recent Successful Backups" to Show > All Backups and / or Check the including boxes for Events where no data is copied and Client Offline errors Even set all the option to ALL to see the big picture and then narrow it down from there Also the backup report is constructed from the Backup Log, the size of which is controlled by Prefs > Notification > Logging > Log Size Limit, although I am sure it should go back further than a couple of days.
×