Jump to content

jotrago

Members
  • Content count

    146
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by jotrago

  1. jotrago

    LTO verification

    I also have faith in LTO read after write technology, so it shouldn't be necessary to verify a tape just to be sure the data is actually on the tape. The drive does that for you. But as you say that doesn't check the rest of the data path. I am a great fan of the, often overlooked, Verify Script (Automate > Manage Scripts > New > Verify). You can set up a verify script, specify all backups sets, and it will only verify outstanding sessions not already verified. {Set the Option "verify only backups not previously verified") For maximum benefit, ensure the MD5 Sums are enabled in Prefs > Media > Verification > Generate MD5 Digests. Set Backup scripts to No Verification so no time is wasted during your backup window with verification. Set your Verify job to run during the day while the backups sets are idle. Retrospect will work its way through the previous night's sessions, verifying them against the MD5 sums in the catalog files, all without touching your clients. How cool is that!
  2. Preferences > Notification > Reporting > "Enable notification for External Applications" I have used this setting in the past with EMC Networker Management Console, and it was quite useful to have the Retrospect event log exported to the external application for monitoring. Now that EMC integration my not be such a priority, can this feature be used in a more generic manner, for instance with a Syslog Server? and if so how? Alternatively does Retrospect have any SNMP integration capabilities?
  3. jotrago

    RetroISA and USB drivers

    This KB article discusses advanced option for ISA in 8.1 http://retrospect.force.com/articles/en_US/Retrospect_Article/RetroISA-Advanced-Options/?l=en_US&fs=Search&pn=1
  4. jotrago

    RetroISA and USB drivers

    I've just got started into Retro 8.1.266 it seems to have addressed some issues with the ISA and USB. I think it used to grab usb disks (and possibly some other devices) to start scanning them, preventing ejection etc. The 8.1.266 fix list mentions several ISA related fixes, including the ability to turn it off altogether.
  5. Backing up Ubuntu

  6. jotrago

    64 bit support

    Environment - Alien 8.86 with Lintian 2.5.6, RetroCLient 7.7.100.rpm I've been trying to install the RetroClient on Ubuntu 1204 64 bit. I am close but not quite there. Alien 8.86 will not convert the rpm package on a 64bit Ubuntu. Presumably becase the RPM is a 32 bit package. So I convert the Package on a 32Bit installation of Ubuntu 1204, which successfully converts the rpm and generates the deb. (It also installs and runs on 32Bit Ubuntu, and I can add the client in the Retro Server) On Ubuntu 64 bit, Attempting to install the deb with sudo dpkg -i complains that it is a 32 bit package. The answer seems to be your method of changing the Architecture line in the Control File. But I can find no way to achieve this. All seem to open the control file read only. I even went as far as attempting to use debreate to rebuild a new package but that got a bit complicated and beyond my skills. So I tried your retroclient_7.6.100-2_amd64.deb after fetching it from the other forum. It seems to install happily, as per your Recipe. I had to install the libc6:i386 (I chose the one for AMD64 platforms from Ubuntu Software Centre which is version 2.15) But I cannot get it to run. When running the update-rc.d I get warnings about Run levels johng@ubuntu12041-Dev:/etc/init.d$ sudo update-rc.d rcl defaults 99 update-rc.d: warning: rcl start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (3 4 5) update-rc.d: warning: rcl stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 1 2 6) On opening rcl the start and stop defaultes ARE set to the recommended values ???? On Running the script the Client doesn't seem to run johng@ubuntu12041-Dev:/etc/init.d$ sudo ./rcl start johng@ubuntu12041-Dev:/etc/init.d$ sudo ./rcl status Retrospect client is not running, I don't see anything with sudo ps -ef If I run the RetroClient.sh script the java GUI Client actually runs So Referring to your Recipe:- How do you get the control file out of the package into an editable state? I don't understand your section # Build binaries $ sudo debian/rules binary How do you rebuild or re-insert the modified control file back into the package? ANy tips would be much appreciated
  7. I have just completed my first Live BMR using the new R7.7 Bare Metal Recovery CD. What a Pleasure. Fortunately I had done a couple of test runs, so when my customer's server crashed both mirrored C: Drive disks simultaneuously, I was able to recover the server in an hour and half. 30 Minutes to replace the faulty drives, reconfigure, raid, mirrors, bios, etc, and 45 minutes to recover ~50G System partiton. I prefer the "Local" method where you run a Retrospect Server from the BMR Disk. Performance is MUCH faster than the Client approach. The new BMR System is simple and effective, just what's needed in a tough DR situation:- The 6 step DR 1. Boot the BMR Disk 2. Prepare, partition, & format the new disk(s). It is important to repeat this process, if necessary, rebooting, till the disks show with their original drive letters. (If you dont, then windows generates tons of errors when it boots, and you will likely have to repeat the whole recovery) 3. Mount the Backup Set(s) (Configuration > Backup Sets > Add > More > Open > point to your Catalog File) 4. Restore Entire Volume, Replacing All Contents, in advanced mode, double check that the System Data & Security is restored. 5. Coffee Break 6. ReBoot There are a couple of provisions which must be done and tested in advance to make it really slick. The key thing is to have the Catalog Files for you Backup Sets available, (If they are simply left in their default locations, you will lose them along with your system drive, in the disaster, and then you will have to re-create them during your DR session, and this process can take HOURS per Backup Set. Definitiely NOT what you need in a DR Situation) My Personal Favourite is to create a Duplicate job or two and Duplicate the Config77.dat, & *.RBC files ( or even the whole Docs & Settings\AllUsers\ApplicationData\Retrospect Folder) to :- At the very least, a non system disk on the BU server, ideally the one with the backup sets on it AND a disk on a different machine, (any Server, Desktop etc which is likely to be available in a disaster) AND an offsite location, or a removable device which is taken offsite Using Duplicate, rather than backup means you simply use the file without having to waste time in the DR recovering Catalog files (Double whammy here, if you don't have catalog files you will, at the very least, have to re-catalog the backup set with the catalog file backup before you can restore them) Even better still, you can control where the Backup Set stores it's catalog files when you create the Backup Set. Set up a directory on a non-system disk and keep them right there. (This can even improve performance by adding spindles to the Retrospect environment.) But don't forget to duplicate them as well. The Second thing is to test your hardware setup so that the Retrospect BMR can actually boot, can See all the Disks, in the correct order, with the correct drive letters, and if necessary access Catalog files and BackUp Sets across the network. You may need to load Drivers for Storage & Network During the Retrospect BMR Boot Process, ensure you have them available and have tested loading them. Ensure you have recorded your disk layout, and lettering scheme, and that you have documented the steps needed to re-create them, particularly running raid configuration utilities, bios setups etc. Practice this if at all possible. I haven't tried it yet but it may be possible to add your own drivers, to the Retrospect BMR iso, using 7Zip or any other iso editor, and thus create a single customised BMR disk (Maybe the Retrospect folks could confirm this? References:- Retrospect Windows 7.7 User Guide Addendum Retrospect Windows 7.7 Release Notes Retrospect User guide (7.5 still seems to be the latest ???) See Manaagement - Moving Retrospect for info on which files to keep to allow instant recovery of Retrospect See Management - Catalog & Configuration Backups to elaborate on my suggestions Good Luck , and may your DR be as painless as mine.
  8. Retrospect does NOT run as a service (Yet - coming in future edition, watch this space:rolleyes:) Retrospect runs as a normal program. However it does have a Launcher Service (see Retrospect launcher in Services) The launcher manages starting and stopping Retrospect to run jobs according the the schedules, or the Scheduled time slots for ProActive. So after a reboot, Retrospect will lauch itself when required Whether you actually see Retrospect running, and whether it stays active after a job has finished is controlled by the Preferences Discussed above. The sources and Backupsets must also be available for ProActive to run, check in the ProActive tab, that the sources are showing as ready, and that the BackupSets are Ready. If they show Media or Failed they may be missing or damaged. Proactive is also controlled by the Default schedule in Prefs, and by Individual Schedules in the Proactive Scripts. Remeber that by definition, ProActive does not run at any fixed time for any given client, based on the frequency you specify in the script it will constantly sort the ProActive backup queue by the longest outstanding backup client, so it is possible there may be times when it has nothing to do. A useful trick, and one that makes remote management easier is to have Retrospect Running Permanently in a Terminal Services Session. That way it is always running, does not interfere with other console activty, and is always available for remote access by RDP. (remember to ONLY close the RDP session dont LOGOFF) THere is a section in the manual about doing this, and see this note
  9. jotrago

    Retrospect Has Lost History And Scripts

    Hi, See this post for answers http://forums.support.roxio.com/topic/74022-lost-my-scripts-and-logs/page__p__370931__fromsearch__1#entry370931
  10. jotrago

    Backup Of Hyper-V Virtual Servers

    Do your Guest OS perhaps have the Data drive configured as Dynamic. From some research I have been doing in anticipation of a couple of my Retrospect customers moving to HyperV, it seems that using Dynamic disks in Guest OS, is not well supported and results in some issues. Primarily a requirement to shut the VM down in order to back it up, if using WIndows own Backup utility. Given that all the disk flexibility you would need is provided in the hypervisor there should really be no disadvantage in sticking to basic disks in the VM. Just a thought
  11. jotrago

    Lost My Scripts And Logs

    Scripts are contained in the Retrospect Config77.dat file along with the whole configuration. By Default It is stored in either Users>AllUsers>Application Data>Retrospect, or Program Data>Retrospect (Locations vary between XP/2003 and 7/2008) The logs are also stored there, unless you have changed the Preferences>Logging options. You can restore the Config.dat file - See Manual / Help Management > Moving Retrospect which discusses dealing with Config77.dat files. or for a more complete discussion on recovering Retrospect DIsaster Recovery>Restoring the Backup Computer Hope this Helps
  12. jotrago

    Restore 6.5 Backup Using 7.7

    R7.7 should be able to read older R6.5 BackupSets (according to the readme & NB the process is not reversible) The procedure would be as follows:- If you have both the original Backup Set data (folder with Axxxxxxxxxxx.rxx files) AND the Catalog file backupsetname.rbc file Then just drag and drop the Catalog file onto Retro and it will Re-instate the backup set, and you can restore using the standard tools. If no Catalog file then you will have to rebuild it Tools>ReCreate Catalog File select "All Disks" and point to the location of the Backup Set data. If it doesnt work right away try one directory higher or lower After scanning the backup set it should re-instate the Backup set into your current Retrospect. See Help / or Manual - Chapter Tools > Maintenance & Repair > Recreating Catalog
  13. jotrago

    How To Set Up Backup Bootable Partition

    From a Retrospect point of view, 7.7 has a nice Disaster Recovery CD (iso included in the distribution). Should you lose your system drive You can boot the system with the CD, then run as either a Retrospect Server or Client, to access either the Backup Set, or Server respectively, and recover your system partition. See my posts on DR http://forums.support.roxio.com/topic/73180-retrospect-77-bare-metal-recovery-rocks/page__view__findpost__p__366871__fromsearch__1 http://forums.support.roxio.com/topic/73181-retrospect-77-bare-metal-recovery-in-client-mode/page__view__findpost__p__366818__fromsearch__1 You might want to check out Roxio Back On Track http://www.roxio.com/enu/products/backontrack/suite/overview.html Alternatively you could use any of the myriad partition cloning tools out there. http://en.wikipedia.org/wiki/List_of_free_disk_cloning_soft Acronis True Image, and I am sure several other products allow you to clone a volume, and then run daily scheduled jobs to update the Cloned copy with changes keeping it up to date. How much of an imprevement did you get putting the OS on SSD?
  14. jotrago

    Erroneous Warning On "restore An Entire Volume"?

    I have recently successfully used the Emergency Recovery CD (7.7.341) with considerable success. Your problem seems a little strange, however two things stand out. 1. You say you are using Restore Files & Folders, surely if you are going to overwrite the entire drive, using Restore Entire VOlume would be the better option. I also found that Advanced mode is better as you can check that the options to recover system state are enabled. 2. Your Error message is showing your LaCie Recovery drive as drive C:, and your Internal Drive as F: My Guess is that you have booted the ER CD and used the Partitioning tools to setup the new disks, and are trying to proceed straight to the recovery. Retro is planning to restore your files to Drive F: and the System State Restore will go to Drive C: hence the warnings. I found that it is necessary to reboot at this point so that the drive letters can be correctly allocated. Presuming that your System Drive backup was from Drive C, you need to Restore it to Drive C.. I made this error and when windows booted I got literally hundreds of errors in the Event Log. My guess was that during the System State restore all references were to F: drive (in your case), instead of C: Bottom line is you need to work with your Storage systems, Raid Controllers, Bios etc until you get to the point that the drives shown By Retrospect in the ER CD system match the order and drive letters as they were at time of backup. I think then Retro will be happy to gracefully restore the backed up C: drive to the NEW C: drive. See also my Separate Post Retrospect 7.7 Bare Metal Recovery Rocks! HTH
  15. I am referring to the Windows "Emergency Recover CD.iso which is included in Retro 7.7.341 in my case specifically. The image is embedded in the Retro .7.7 download file (accessible with a License). You can also download it directly if you have a valid 7.7 license from here :- http://download.dantz.com/gate/bmr.php This is a universal Windows Boot CD, which boots a Microsoft PE and offers to Run either a Retrospect Server or Client The new EMR CD included with Retro 7.7 is very different from the previous approach used in Retro 7.6. Retro 7.6 required a more elaborate scheme whereby a recovery CD had to be "Prepared" from backups, producing a CD specific to a particular machine. I never used this method, and cannot comment on it's effectiveness.
  16. jotrago

    Selectors Headaches

    You also mention including selectors within other selectors, This is possible, if a little mind bending. However once you get your head around it, it is very powerful, and flexible. After much research and practice I have concluded the following Nesting Selectors Retrospect Selectors have sections to INCLUDE and EXCLUDE specified items EXCLUDES always take priority over INCLUDES One is able to 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} 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 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 (relatively small) 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. Hope this helps
  17. jotrago

    Selectors Headaches

    Backing up just a few files from a large volume with Retro, has it's challenges. I went through the same thing some time back. The problem is not so much setting up the volume and selectors for what you want to achieve, but in the way Retrospects works with it's snapshots and progressive backup. The key thing to understand is that whenever a backup runs, Retrospect takes a snapshot of the ENTIRE volume, and it does this first, BEFORE applying your selector. This can result in the "Scanning" taking a long time, and then the actual backup of the few files is quick. The Session however will reflect only your "Few Files" Further if you do a Replace Entire Volume restore for your "Few Files" backup, it will restore the entire (albeit empty) directory structure for the volume, along with your "Few Files". a "Files & Folders" restore should work as expected.
  18. jotrago

    Retrospect Insights And 2011 Roadmap

    In a recent exchange with Retrospect support on a case it was hinted that a Service model for Retrospect may be on the todo list, for an upcoming major windows version.
  19. I recently tested the new BMR Recovery disk, which I found very simple to use, and very effective. It's a great addition to Retrospect. However I did notice that the network performance I achieved when running the BMR in client mode was much less than running the normal client in Windows. The standard client performance as per the Client Refresh test was 11-12 MB/s as expected on 100Mb/s Ethernet The client on the BMR disk would only register ~2MB/s or one 5th the speed???? on the same hardware. Using the Local Server Mode gave excellent performance, so I will be configuring my customers to maximise the possibility of using Local Server mode, by ensuring that Backup Sets and Catalogs are available on a locally accessible disk.
×