Drive Image 7 scheduled backups

[Nanga Parbat]

What I want to achieve with Drive Image 7 is a daily backup from
monday through friday at 10pm whereby the previous backup file is
overwritten. I created a weekly shedule where I limited the number of
backup files to 1 but it still creates file001, file002,... Is there a
way to avoid this?

Nanga

 

[Rod Speed]

What I want to achieve with Drive Image 7 is a daily backup from
monday through friday at 10pm whereby the previous backup file
is overwritten. I created a weekly shedule where I limited the
number of backup files to 1 but it still creates file001, file002,...

You sure that isnt just DI splitting a single image file into
2GB chunks ? It always does that for various reasons.

Easy enough to prove by watching what happens
files wise after the monday backup and the tuesday
backup and using the timestamp on those files.

Is there a way to avoid this?

It's be pretty easy to do what you like behind its back with a
scheduled op outside DI to delete the files you dont want etc.

Bit safer too because you dont want a flakey hard drive
preventing the successful creation of the image file and
not having the previous image file to restore from, because
its been deleted at the start of the unsuccessful image creation.

 

[Nanga Parbat]

You sure that isnt just DI splitting a single image file into
2GB chunks ? It always does that for various reasons.

Nope, but I've done some further testing. First day file001 is
created, second day DI creates file002 but after that deletes file001.

Easy enough to prove by watching what happens
files wise after the monday backup and the tuesday
backup and using the timestamp on those files.

It's be pretty easy to do what you like behind its back with a
scheduled op outside DI to delete the files you dont want etc.

Of course that's possible. I was just wandering if DI could do it.
Saves me some configuration work

Bit safer too because you dont want a flakey hard drive
preventing the successful creation of the image file and
not having the previous image file to restore from, because
its been deleted at the start of the unsuccessful image creation.

The risc is calculated. The stategy is a first disk where all the work
is done. A second disk that contains only images of the first disk. A
tape streamer that takes a complete backup of the second disk. On top
of that the first disk is in fact 2 disks in a raid-1 setup.

That way we have backups on the second disk for fast recovery and
historical backups on tape that can also be stored at a different
location.

I feared not having enough place on the second disk in the future if 2
copies have to exist for some time. I can however minimize that
problem by using a higher compression.

Anyway, this isn't likely to happen is the first couple of years
(which is a risc by itself because by then you have forgotten there's
a risc ). A nice feature in DI7 is notification. Everytime DI does
something I'll receive an e-mail. Whenever I receive a complaint about
not enough disk space I can take immediate action, meaning they need
to buy a bigger disk. That's good for business

Nanga

 

[Tom]

What I want to achieve with Drive Image 7 is a daily backup from
monday through friday at 10pm whereby the previous backup file is
overwritten. I created a weekly shedule where I limited the number of
backup files to 1 but it still creates file001, file002,... Is there a
way to avoid this?

Nanga

DI7 is a product that should never have been released.
They haven't tested the crap and they refuse to anser all support calls.
I'm going to send my correspondence to the Symantec CEO.

I had a similar issue with a McAfee product, after being a life long
customer.
Looked up the CEO on Yahoo Finance and emailed him and several VPs.
Had customer support on the phone that day for a couple of hours until they
fixed their problem.

 

[Fred Martin]

DI7 is a product that should never have been released.

You are the absolutely classic arguement for retrospective abortion.

They haven't tested the crap

Obvious mindless silly stuff.

and they refuse to anser all support calls.

Only from scum like you.

I'm going to send my correspondence to the Symantec CEO.

Who will just flush it where it belongs.

I had a similar issue with a McAfee
product, after being a life long customer.

There might just be a message there, child.

Looked up the CEO on Yahoo Finance and emailed him
and several VPs. Had customer support on the phone that
day for a couple of hours until they fixed their problem.

Wanna bet about Symantec ?

 

[CWatters]

Nope, but I've done some further testing. First day file001 is
created, second day DI creates file002 but after that deletes file001.

Normally if you tell it to keep two backup sets it waits until it has
verified the THIRD then deletes the first (eg so you have two copies
remaining). If you tell it to keep just one copy I image that it will create
a second then delete the first. It does this do that at no time do you have
_no_ copies.

 

[CWatters]

It does this do that at no time do you have _no_ copies.

That should read "It does this so that at no time do you have _no_ copies."

 

[Joep]

DI7 is a product that should never have been released.

Runs absolutely fine here, no problems what_so_ever ...

They haven't tested the crap and they refuse to anser all support calls.

probably called ID ... Look, there's that moron again, let's see and find
out how long he can stand the awful music.

I'm going to send my correspondence to the Symantec CEO.

Pffft ... like that guy hasn't anything better to do.

I had a similar issue with a McAfee product, after being a life long
customer.
Looked up the CEO on Yahoo Finance and emailed him and several VPs.
Had customer support on the phone that day for a couple of hours until they
fixed their problem.

I did tech support jobs, we laughed about pitty ass worms like you and so
did our CEO.

 

[Tom]

Runs absolutely fine here, no problems what_so_ever ...

Listen up Rod Speed ****wit, you probbaly don';t even know how to partition
drives into 5 partitions and therefore, aren't using the produict the way I
am and which is supposed to work.

probably called ID ... Look, there's that moron again, let's see and find
out how long he can stand the awful music.

I used Symantic's web support contact page, since that is the only way you
can contact them without paying them $30 to $90, which is ****ing
rediculous.
I paid $70 for their product and it doesn't work.

Pffft ... like that guy hasn't anything better to do.

Uhh, yeah like stand in the ****ing unemployment line when his company falls
over for lack of tech support!
Funny, but I was contacted and the issue resolved with McAfee immediately.
They have their shit together. Symantic does not.

I did tech support jobs, we laughed about pitty ass worms like you and so
did our CEO.

Which is why you are both unemployed, ****wit Rod Speed!

 

[Rod Speed]

Pathetic little pig ignorant ****wit is so stupid
that it cant even manage to work out that Joep
and me are on opposite sides of the world.

And when its that stupid, its hardly surprising that it cant use DI either.

Runs absolutely fine here, no problems what_so_ever ...

Listen up Rod Speed ****wit, you probbaly don';t even know how to partition
drives into 5 partitions and therefore, aren't using the produict the way I
am and which is supposed to work.

probably called ID ... Look, there's that moron again, let's see and find
out how long he can stand the awful music.

I used Symantic's web support contact page, since that is the only way you
can contact them without paying them $30 to $90, which is ****ing
rediculous.
I paid $70 for their product and it doesn't work.

Pffft ... like that guy hasn't anything better to do.

Uhh, yeah like stand in the ****ing unemployment line when his company falls
over for lack of tech support!
Funny, but I was contacted and the issue resolved with McAfee immediately.
They have their shit together. Symantic does not.

I did tech support jobs, we laughed about pitty ass worms like you and so
did our CEO.

Which is why you are both unemployed, ****wit Rod Speed!

 

[Joep]

Listen up Rod Speed ****wit, you probbaly don';t even know how to partition
drives into 5 partitions and therefore, aren't using the produict the way I
am and which is supposed to work.

You think highly of yourself moron, I am afraid your arse is blocking your
view on reality. The fact that I do use the product as intended on several
multi disk, and multi partitioned systems while you can't, suggests I seem
to know a little more than you.

I used Symantic's web support contact page, since that is the only way you
can contact them without paying them $30 to $90, which is ****ing
rediculous.

When having to deal with morons like you it seems underpriced.

I paid $70 for their product and it doesn't work.

You payed $70 and *YOU* can't get it to work

Uhh, yeah like stand in the ****ing unemployment line when his company falls
over for lack of tech support!
Funny, but I was contacted and the issue resolved with McAfee immediately.
They have their shit together. Symantic does not.

Well, having to contact a CEO getting support to answer you hardly sounds if
they have their shit together ... Anyway I don't care if they have their
meals together, or have their shit together either ... maybe it's why they
didn't answer your call, they were having their mutual shit session ... try
again later.

It's a timer in the product, trying to get rid of life long morons like you.

 

[Tom]

way

You think highly of yourself moron, I am afraid your arse is blocking your
view on reality. The fact that I do use the product as intended on several
multi disk, and multi partitioned systems while you can't, suggests I seem
to know a little more than you.

Yopu are an idiot and a liar.
I have buit over a thousand systems and as fasr as I know, they are all
still running fine.

When having to deal with morons like you it seems underpriced.

I write software and hardware IP for a living, moron.

You payed $70 and *YOU* can't get it to work

Because it doesn't work ftard. It does not expand a source partition to the
destination size, as advertised.

Well, having to contact a CEO getting support to answer you hardly sounds if
they have their shit together ... Anyway I don't care if they have their
meals together, or have their shit together either ... maybe it's why they
didn't answer your call, they were having their mutual shit session ... try
again later.


It's a timer in the product, trying to get rid of life long morons like

you.

Back to the white room for you, along with back in the killfile you ****ing
tech reject.

 

[Michael Cecil]

Because it doesn't work ftard. It does not expand a source partition to the
destination size, as advertised.

I use Ghost normally, but I just tried DI7 and it had no problem expanding
a source partition to fit a larger target destination. I think you must
not have understood the instructions. Did you read them?

 

[Joep]

Yopu are an idiot and a liar.
I have buit over a thousand systems and as fasr as I know, they are all
still running fine.

Hmm... maybe time to check that first .... 'as far as I know' isn't hardly
re-assuring

I write software and hardware IP for a living, moron.

The 'write software part' I understand (though I am still not impressed, you
could be writing complete garbage - probably if you can't even get something
as simple as DriveImage to work). And then you write 'hardware' as well? How
should I take this? The fact you 'wrote' hardware we can all see. If I
actually write down "you're a clown", then I do not have to mention that I
write "you are a clown", I just write it down.

Because it doesn't work ftard. It does not expand a source partition to the
destination size, as advertised.

Again, *YOU* can't get it to work, so obviously you are the retard.

sounds
you.

Back to the white room for you, along with back in the killfile you ****ing
tech reject.

Heh heh heh ... Mr. retard is getting all worked up ;-) ... Killfile ... do
I need to explain how that works?

 

[Tom]

I use Ghost normally, but I just tried DI7 and it had no problem expanding
a source partition to fit a larger target destination. I think you must
not have understood the instructions. Did you read them?

--
Michael Cecil
(e-mail address removed)
http://home.comcast.net/~macecil/howto/
http://home.comcast.net/~antiviruscd/

If you have an old drive partitioned into five, and a destination drive
partitioned into five larger partitions, it does not expand each of them
when retsoring one partition.
It does not work and I had someone else attempt the same thing, with the
same results.
I did what the manual says it supports and it does not.
The instructions and options available in the software are limited to but a
couple of choices and all were tried several dozen times.
It's pretty simple; it does not do what it says it does.

 

[Michael Cecil]

If you have an old drive partitioned into five, and a destination drive
partitioned into five larger partitions, it does not expand each of them
when retsoring one partition.
It does not work and I had someone else attempt the same thing, with the
same results.

How would it expand "each of them" when you're just restoring one
partition? Maybe you just don't understand the terminology.

I did what the manual says it supports and it does not.
The instructions and options available in the software are limited to but a
couple of choices and all were tried several dozen times.
It's pretty simple; it does not do what it says it does.

Sure it does. Your knowledge or methodology must be faulty.

 

[Tom]

How would it expand "each of them" when you're just restoring one

partition? Maybe you just don't understand the terminology.

Because I imaged each partition separately and attempted a restore of each
separately and it is supposed to expand the data to fill the destination
partition.
In winxp, this option is grayed out, so I used the CD boot program and it
allows a deletion of the data on the partition and is then supposed to
expand the imaged partition to the new partition size.
However, after booting, winxp reports the partition as being the size of the
old drive.
This is how it 'doesn't work'.

Sure it does. Your knowledge or methodology must be faulty.

--

No, it's not.