#1
|
|||
|
|||
Converting to 2.6.2
I have a question regarding whether it is normal for SD to automatically change the "Name" of my Primary BackUp Schedule from: "Smart Update Seagate 1Boots" TO "Smart Update Seagate 1Boots 1"?
This was done while I was establishing my new schedules after having updgraded. I am afraid that SD will not recognize the new name since I have no scheduled back-up that has that trailing "1" on it. What should I do as I don't want to trigger a full blown non-smart update that normally takes 12 hrs or so. Please help. Add-on... should I delete my old schedules prior to the first 2.6.6 back-up.
__________________
Bruce Last edited by thxbruce; 01-06-2010 at 06:33 PM. Reason: Forgot to add this. |
Tags |
v2.6.2 upgrade anamoly |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Glitches with SD! 2.6.2 and target disk image selection | Timmy | General | 9 | 03-24-2010 10:51 PM |
Thanks for 2.6.2! | Herbert Schulz | General | 1 | 10-19-2009 04:16 PM |
Converting TM backup direct attached volumes to network attached volume such as TC | barrysharp | General | 1 | 03-25-2008 12:29 PM |
Converting Read-Only to Read-Only? | wheelermj | General | 3 | 02-27-2008 09:47 PM |
'Converting to read-only using high compression' | patrickmast | General | 2 | 08-14-2007 07:57 AM |