Hello everyone. I'm a huge fan of the product and have been using it for many years now. I'm slowing working my way to Virtual Machines and have settled on Citrix XenServer. Fantastic product. Anyway, I'm moved my servers over to it and one in particular has my concern. I've never used IFW to backup a running exchange server's Data partition. I'm quite comfortable with running a backup of the OS partition of MS Server with Exchange loaded on it... but what about the Exchange data volume?? I'm used to running a backup from a BING CD, or an Exchange specific backup package, like NTBackup or BackupExec. Anyone rely on using IFW, while Exchange is running? It usually takes about an hour. I'm worried some db tables will get messed up.
Anyway, thanks for listening! Let me know your thoughts.
with best regards,
Chuck
IFW - Exchange Data Volumes ???
-
TeraByte Support
- Posts: 3613
- Joined: Thu May 05, 2011 10:37 pm
Re: IFW - Exchange Data Volumes ???
If you are using databases such as SQL Server or Exchange Server with the
..LOG and Database files on physical separate drives (or partitions if only
backing up that single partition) then you should ensure that the service
is stopped before PHYLock or VSS starts. Furthermore, all partitions that
contain the various files should be backed up at the same time due to the
relationship between the .LOG (transactions) and Database (data) files. If
both types of files are located on the same partition (or doing a full-drive
backup where both files are on the same physical drive) then the service can
remain running during the backup.
You can also control services using the services.ins file (see manual for
details). For example, you could shutdown a service and have it start again
as soon as PHYLock starts.
"computerchuck" wrote in message news:2550@public.image...
Hello everyone. I'm a huge fan of the product and have been using it for
many years now. I'm slowing working my way to Virtual Machines and have
settled on Citrix XenServer. Fantastic product. Anyway, I'm moved my
servers over to it and one in particular has my concern. I've never used
IFW to backup a running exchange server's Data partition. I'm quite
comfortable with running a backup of the OS partition of MS Server with
Exchange loaded on it... but what about the Exchange data volume?? I'm
used to running a backup from a BING CD, or an Exchange specific backup
package, like NTBackup or BackupExec. Anyone rely on using IFW, while
Exchange is running? It usually takes about an hour. I'm worried some db
tables will get messed up.
Anyway, thanks for listening! Let me know your thoughts.
with best regards,
Chuck
..LOG and Database files on physical separate drives (or partitions if only
backing up that single partition) then you should ensure that the service
is stopped before PHYLock or VSS starts. Furthermore, all partitions that
contain the various files should be backed up at the same time due to the
relationship between the .LOG (transactions) and Database (data) files. If
both types of files are located on the same partition (or doing a full-drive
backup where both files are on the same physical drive) then the service can
remain running during the backup.
You can also control services using the services.ins file (see manual for
details). For example, you could shutdown a service and have it start again
as soon as PHYLock starts.
"computerchuck" wrote in message news:2550@public.image...
Hello everyone. I'm a huge fan of the product and have been using it for
many years now. I'm slowing working my way to Virtual Machines and have
settled on Citrix XenServer. Fantastic product. Anyway, I'm moved my
servers over to it and one in particular has my concern. I've never used
IFW to backup a running exchange server's Data partition. I'm quite
comfortable with running a backup of the OS partition of MS Server with
Exchange loaded on it... but what about the Exchange data volume?? I'm
used to running a backup from a BING CD, or an Exchange specific backup
package, like NTBackup or BackupExec. Anyone rely on using IFW, while
Exchange is running? It usually takes about an hour. I'm worried some db
tables will get messed up.
Anyway, thanks for listening! Let me know your thoughts.
with best regards,
Chuck