Jump to content

tchannon

Members
  • Posts

    11
  • Joined

  • Last visited

tchannon's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Adding information. W8.1 and W10 still suffer erratic power profiles and erratic scheduler, maybe maybe not, maybe tomorrow, etc. Backup is likely to be disrupted by the computer going to sleep. (when the computer _will_ decide to notice the power settings :-) ) If you are scripting backup an answer is switch power plan. Create a backup power plan, can be done via the GUI. A command which can be executed via script or by hand from a console is powercfg.exe powercfg /LIST Returns a list of plans, with the active one marked with a * powercfg /S <GUID> Set a plan active. So, get the plans, parse. Save the active plan GUID, set backup plan, do the backup, restore old active plan. (decided I don't like W10, reverted to 8.1)
  2. For reference Scenario, Windows later than XP, user runs without administrator privileges, user does backup needing interactions such as to DVD. Retrospect is unable to schedule launch the Retrospect UI, reason, Retrospect cannot bypass UAC, a security crossing. One workaround is open the Retrospect UI before a scheduled backup. Unfortunately if this is not done and a schedule runs it opens a "silent" UI for admin with the only cure a forcible process termination by admin. The following workaround has been tested on W8.1 with R, 7.7, backup to DVD. Multiple backups, some via network and with rotating backup media sets. Unfortunately this requires some degree of programming skill, perhaps adjustment of disk system permissions. The basic idea is use Microsoft Scheduler to launch Retrospect. This is done indirectly. The scheduler runs a user script or program which looks at the system clock and launches Retrospect with the correct backup to be done for that day and perhaps time. The Retrospect scheduler is not used at all. Lets assume we have two rotating backups run alternate weeks on a Tuesday and to two backup sets, A and B. In Retrospect create a script with backup up and to those sets A and B, perhaps with WOL (wake on lan) enabled, software compression enabled, and eject media enabled, definitely a checksum disk check if it is DVD. No schedule. (Retrospect handles failed file checksum by marking it not backed up, is not forgotten, either needs a second run or will get backup next time, provided you are careful with disks, no problems, I used +RW, improve with use, good for 100+ and maybe many more rewrites, just don't drop or touch or scratch) Now, go to menu Run and select the script. Select say backup set A and create a run script, carefully saving in the run script directory with an edited filename eg. Fred backup.rrr ==> Fred Backup A.rrr And do it again selecting backup set B Fred backup.rrr ==> Fred Backup B.rrr If you were to doubleclick Fred Backup B.rrr the UI would open and a backup would start. You have to produce a program which sees the date, works out the day of week and on alternate weeks executes the cmd Fred Backup A.rrr or Fred Backup B.rrr Doing this is obviously involved but there are the basics. When the UI opens it will demand an admin password. The user program could do lots of things. As it stands it will show itself on the taskbar as well as Retrospect, this is fixable. A log file might be useful. In theory it could even be done using batch language, lots of tool choices. Windows scheduler, set this up for the user who will be logged in, not for admin. Be a good idea to set the working directory to the script directory. You might find it useful to have the directory where the script reside in admin documents but with the logged in user granted access rights to that directory. Tip to stop headache, getting the computer date is left as an exercise and so is converting the date to a julian date. local select = (julian % 7) % 2 Modulo 7 gives weeks, modulo 2 gives 0 or 1 for even or odd weeks, working around Gregorian calender nonsense (Julian days are a contiguous.number set, no year breaks) I already have d.wday if d.wday == 4 then -- in this case is Wednesday In this case where fn is set, ret = os.execute('"' .. fn .. '"') That adds quotes around the Retrospect filename... because it may contain spaces. If you _really_ have UAC problems there are workarounds involving Scheduler and calling Shortcuts... which call what you finally want. Shortcuts allow permissions. Foolproof? No. Good luck.
  3. Possible but slow, unergonomic, UI causes me problems. I'm steering clear of anything slowing shutdown, slow as it is. I didn't reply immediately, wanted to see how things panned out. It tripped WOL, and went through to wanting media so all being well I have a workaround. Thrown away the Restrospect scheduler, written out run scripts for all rotate versions of all versions of backup. I'd have written them on the fly but it turns out there are dirty tricks going on, can't figure it so this is simplest. (what appear to be plain scripts have secret baggage, file contents and size differ) Win Scheduler calls a Lua script at one of the backup start times, it figures out which backup set based on time and date and invokes Retrospect which asks for a password. A variety of ways of doing this, Lua is to hand and is flexible.
  4. Having thunk and fiddled, it is worse than I assumed. If a scheduled item fires it jams, has to be manually killed as a task under admin before the UI can be run at all. There are a pair of candidate workarounds: - 1. Ignore the Retrospect scheduler and write an external invoker, not quite triival where there are rotating back sets. 2. No dice so far but if the Restrospect scripting or something else can send a message *before* trying to launch the UI and get jammed waiting for a "carry on". The message receiver does the UI launch. I find the scripting a bit opaque but so far as I can see it doesn't send before trying the UI. Or hairier fixers. Any ideas?
  5. Oh. Thank you (really) for the news on life is like that :-) Bit of a whoops. Thinking about this it only makes partial sense so lets try and figure it out. A system task isn't able to launch a UI for the logged in user. (whether this is strictly so cannot as a negative be proven) However, if the user has the UI open it can interact with a system task which starts. On the other hand if the system task has started a newly started UI cannot interact but does know something is active. This implies the scheduler is not a lot of use so maybe external control is a viable idea. Not so far. The MS scheduler silently fails to run Retrospect, although to be fair there is little it will run if it has a GUI. A solution of leave the Retrospect UI open not acceptable. I'll think on what to do.
  6. I'm out of ideas persuading a scheduled backup run to appear to the logged in user, ie. me where I do not run as an administrator. Direct usage is no problem, such as executing the same script from the keyboard. Clarifying, the schedule fires, perhaps starting a network client backup but never appears to the logged in user or asks for media. I can see it in tasks. I originally installed from my usual account, worked as above. Tried uninstall and install logged in as admin, same result. Tried all I think of to do with permissions. This is V7.7, last upgraded shortly before 8 was released, and run on locked down XP Pro without more than the usual problems. In this case it is running under 8.1 Home. I don't see why this version will not work, does all I need.
  7. News. After a lot of pain 7.7 has settled down, completing several successful backups on the complete network here and showing a restore is feasible via a trial. (my existing experience tells me there is no need to actually do the whole exercise) This was done on a trial licence, which didn't complain about expire soon (good). I've now paid. three emails were received (instant), invoice/receipt and new licence code the critical ones. Licence updated without problem. (unlike the old days when it could take months to get a take) The UI is still poor and illogical/indirect speaking. How it is. Defects? Found several which I ought to have recorded but there is so much needs a rewrite seems pointless. One I recall is discovering it doesn't handle it's own configuration correctly, so on changes to drive config, exit and rerun, then it picks it up. Get it setup and it works. DVD handling is okay but I did need to force in a non-Microsoft ASPI driver, a known problem, nothing to do with Restrospect. Bit of a story. If anyone with XP suspects this is an issue the simplest current recommendation is install **only from the official site** the now free usage read only InCD package from Nero who bought the rights from Adaptec ages ago. The critical point is this installs a good commercial ASPI driver. (Frog driver works but few will trust an unknown third party) If this embarrasses the new owners of Retrospect, simple answer. Critical file in system32 is wnaspi32.dll, Nero version 2.01 dated 2006 I notice eject media after backup (config item) now seems to work reliably, used to very erratic. New media verify function is a great improvement (checks against checksums after end of writing) Update client over the network works fine. (always did for me anyway) Client works fine. I use separate workstation wake on lan and shutdown to hibernate as needed here. (best software for this is the wonderful tools from sysinternals, so good MS bought the company ... note: this will NOT work with Home versions of the OS) http://technet.micro...ernals/bb897553 (microsoft site) There seems to be a speed problem, backs up somewhat slower than V6.5 but doesn't seem to be caused by bloat. Can't keep the DVD write satisfied. Suspect this is about drive handling/buffering. (existing observation, an external drive tends to run faster) Been able to trip exceptions, if under fault conditions. It works which is what matters.
  8. That was painful. Good news is it probably works. For the record. Two XP Pro boxes on a wired LAN workgroup. Initially Retrospect Professional 6.5 Backup to DVD +RW via NT Passthrough. Couple of drives died over time, last one was external on USB2 New SATA drive where 6.5 autoconfigures the drive but it doesn't actually work. Drive reports as TSSTcorp CDDVDW SH-S223L firmware S03 Filled in the form and downloaded R7.7 (100M +). Email arrived giving trial software key. Dealing here with the master XP box which will carry the full Restrospect, the other box is a network client. Uninstalled R6.5, seemed to work but I looked anyway, service still running. Reboot. Service still running, no uninstall item. Check old program directory, empty except for preserved user content (good behaviour). Exe and dll are missing so service isn't actually usable. Run registry cleaner, finds nothing. Start regedit and search on dantz Delete dozens of keys. Double check, none left. Reboot, service has gone. Run registry cleaner, finds nothing. I know there are some configuration directories deep in the file system, decide to leave them, assuming 7.7 won't find them. Install 7.7, no problem but says it is upgrading, ouch, has found something, give it the emailed key, is happy. Reboot, paranoid is'us Bad stuff omitted. (I was scratching trying to figure things out) Go into devices, select the DVD and delete the autoconfig... however this is where R, is dreadfully done, nothing tells you whether a configre exists or properly what it is doing, including messages vanishing off the end of text boxes. Drive is not recognised but doesn't tell you. Therefore run autoconfigure. Changed behaviour from R5 or R6, read the prompts. Odd. That is what ought to happen. I went through waiting for ages, nothing doing. Some were not crashes, but I've has exceptions from CPP and as far as needing to forcibly close R. This was all about the DVD and getting configure to work. It suddenly behaved. (several reboots for sanity sake, wise after crashes) Is this computer stable, yes. Fully patched etc. Since then it has behaved. Tried a small test backup with full DVD verify. (note, to do the master no client is installed) Restored the backup to a different location. All okay. Boot the other (client) XP box (via wakeup). Wait. Add client, it finds the client, select, it asks for a password (Restrospect 6.5 client password), give it. And we have details, all fine. Hit upgrade client (this was you-must-be-kidding), few seconds reports okay. Didn't reboot the client. (I'm not usually into lots of reboots) Create a new client DVD dataset. Create a backup script as normal for that client. Advanced turn on backup security settings etc. Trip an immediate backup on the schedule client script. Asks for disks, formats, and does it in three. Speed is fairly normal (and much worse than with a USB drive), how it is. It goes into verify and asks for the disks again. Zero errors. Reports mentions rather poor compression 19% but much the same as 6.5, just how it is. That's it. I've now created additional backup sets and added these to the client script, scheduled as a rotation. And also for the master XP box, which has yet to be run... which will take many more disks. Did 7.7 read 6.5 DVD? Not sure. It did read disk labels but said the disks are unknown. This is worrying for anyone needing to restore an old system. It is possible I had some bad disks, so that this as uncertain. Might help someone. Any questions?
  9. Looks like swallow hard and risk a trial version.
  10. Recreating a catalogue of what is in a tape/disk/whatever "backup set" is in my experience straightforward. Normally you keep a copy on hard disk but as you realise this can be recreated from the media. No problem so far. Devices. Ouch. Retrospect will list the computer devices it can see at the moment but this does not mean they are configured and active for use by Retrospect. As far as I can recall it has to be told to use a device and perhaps configured by doing tests on media (awkward if you have no definite spare tape) Guessing because I have never seen V7, if you right click on the device entry in the list there will be a menu item about configuring/using that device. If R. knows about the device/model it is just a matter of select it from the listings (long time since I used a tape drive). Assuming this works the rest is relatively easy.
  11. I'm a long time user on MS machines including in the past on servers. Personally I use Professional on a local workgroup, have done for many years, currently on 6.5 Back then Dantz tended to be a "difficult" company with no reasonable support, followed by in essence failure and a long saga as you know. My reading was interest kind of moved to Apple, dead product but what I had was workable. Alternatives still don't exist, at least at a sane price. (moment you mention network, the $$$ jump) Very recently the last workable backup drive here failed, not a surprise. It is not possible to just go and buy a new drive because only some work with R,, I have a new SATA drive, no dice. I was already aware some kind of vendor movement was taking place with Retrospect, if appearing highly unstable. The ongoing problem is NT passthrough as access to optical drives, a known unreliable facility generally but many products manage this without trouble, nor is there any actual problem here for other software. Retrospect is extremely sniffy about APSI so I have been through hell many times, having to resort to things like the Frog driver, currently the Nero driver. It's a black mark against Retrospect that it uses special disk formats instead of a standard filing system. This gets into the ridiculous such as drive testing to see if it works. Even if this passes it is no guarantee it actually works. (current situation here, complains it doesn't recognise a disk as valid, says unknown but after passing tests) Version 7.x now exists. The drive compatibility list is still a joke. Nothing is said about what might work or has changed, no change from the old days. I am using XP and DVD for backup. Any suggestions on whether 7.x might be fixed? Coda: I've had quite a few hard disks go down over the years and also server hardware failures. Recovery has worked fine. As a system I know it works for real. Lots of things could be better. Tim
×
×
  • Create New...